From: syzbot <syzbot+list402b67683d6a416b29ea@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Oct 2026)
Date: Mon, 26 Oct 2026 13:33:43 -0700 [thread overview]
Message-ID: <6adfb927.3a3d6196.2ecadf.0022.GAE@google.com> (raw)
Hello net maintainers/developers,
This is a 31-day syzbot report for the net subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/net
During the period, 7 new issues were detected and 6 were fixed.
In total, 58 issues are still open and 1801 have already been fixed.
There are also 34 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1034 No INFO: task hung in netdev_run_todo (4)
https://syzkaller.appspot.com/bug?extid=894cca71fa925aabfdb2
<2> 917 Yes INFO: task hung in tun_chr_close (5)
https://syzkaller.appspot.com/bug?extid=b0ae8f1abf7d891e0426
<3> 644 Yes WARNING in inet_sock_destruct (6)
https://syzkaller.appspot.com/bug?extid=5b3b7e51dda1be027b7a
<4> 554 Yes INFO: task hung in nsim_destroy (4)
https://syzkaller.appspot.com/bug?extid=8141dcbd23a8f857798a
<5> 520 No possible deadlock in __ipv6_dev_mc_inc
https://syzkaller.appspot.com/bug?extid=afbcf622635e98bf40d2
<6> 203 Yes BUG: Bad page state in skb_pp_cow_data
https://syzkaller.appspot.com/bug?extid=ff145014d6b0ce64a173
<7> 45 Yes UBSAN: array-index-out-of-bounds in llc_conn_state_process (2)
https://syzkaller.appspot.com/bug?extid=628f93722c08dc5aabe0
<8> 40 Yes WARNING: suspicious RCU usage in phy_detach
https://syzkaller.appspot.com/bug?extid=694b49f41098a5df4fd7
<9> 29 Yes WARNING in dev_shutdown (7)
https://syzkaller.appspot.com/bug?extid=c9ecf60a8adb7629821e
<10> 25 Yes INFO: task hung in inet6_rtm_deladdr (3)
https://syzkaller.appspot.com/bug?extid=55141a0ffa0d17f01c71
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2026-10-26 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6adfb927.3a3d6196.2ecadf.0022.GAE@google.com \
--to=syzbot+list402b67683d6a416b29ea@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®