From: syzbot <syzbot+list9d8ba8e7238408167f9d@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Sep 2026)
Date: Fri, 25 Sep 2026 05:33:38 -0700 [thread overview]
Message-ID: <6ab66a22.80e1c6cc.1e8e5f.0032.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 15 were fixed.
In total, 56 issues are still open and 1793 have already been fixed.
There are also 30 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 816 Yes INFO: task hung in tun_chr_close (5)
https://syzkaller.appspot.com/bug?extid=b0ae8f1abf7d891e0426
<2> 641 Yes WARNING in inet_sock_destruct (6)
https://syzkaller.appspot.com/bug?extid=5b3b7e51dda1be027b7a
<3> 509 No possible deadlock in __ipv6_dev_mc_inc
https://syzkaller.appspot.com/bug?extid=afbcf622635e98bf40d2
<4> 500 Yes INFO: task hung in nsim_destroy (4)
https://syzkaller.appspot.com/bug?extid=8141dcbd23a8f857798a
<5> 126 No INFO: task hung in rxrpc_destroy_all_calls (4)
https://syzkaller.appspot.com/bug?extid=1c21ab751f6531a595d6
<6> 43 Yes UBSAN: array-index-out-of-bounds in llc_conn_state_process (2)
https://syzkaller.appspot.com/bug?extid=628f93722c08dc5aabe0
<7> 2574 Yes INFO: task hung in addrconf_dad_work (5)
https://syzkaller.appspot.com/bug?extid=82ccd564344eeaa5427d
<8> 1209 Yes INFO: task hung in switchdev_deferred_process_work (3)
https://syzkaller.appspot.com/bug?extid=d6bbe0f5705cb8a5aa2b
<9> 676 Yes INFO: rcu detected stall in tc_modify_qdisc
https://syzkaller.appspot.com/bug?extid=9f78d5c664a8c33f4cce
<10> 252 Yes INFO: rcu detected stall in rtnl_newlink (5)
https://syzkaller.appspot.com/bug?extid=2e90866706ad999df132
---
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-09-25 12: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=6ab66a22.80e1c6cc.1e8e5f.0032.GAE@google.com \
--to=syzbot+list9d8ba8e7238408167f9d@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®