From: syzbot <syzbot+list5e1151440ec5d571ba68@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Jul 2026)
Date: Fri, 24 Jul 2026 21:32:33 -0700 [thread overview]
Message-ID: <6a643c61.a2ea2cc8.fbad6.0011.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, 2 new issues were detected and 7 were fixed.
In total, 56 issues are still open and 1759 have already been fixed.
There are also 29 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4131 Yes INFO: task hung in synchronize_rcu (4)
https://syzkaller.appspot.com/bug?extid=222aa26d0a5dbc2e84fe
<2> 937 No INFO: task hung in netdev_run_todo (4)
https://syzkaller.appspot.com/bug?extid=894cca71fa925aabfdb2
<3> 690 Yes INFO: task hung in tun_chr_close (5)
https://syzkaller.appspot.com/bug?extid=b0ae8f1abf7d891e0426
<4> 639 Yes WARNING in inet_sock_destruct (6)
https://syzkaller.appspot.com/bug?extid=5b3b7e51dda1be027b7a
<5> 491 No possible deadlock in __ipv6_dev_mc_inc
https://syzkaller.appspot.com/bug?extid=afbcf622635e98bf40d2
<6> 447 Yes INFO: task hung in nsim_destroy (4)
https://syzkaller.appspot.com/bug?extid=8141dcbd23a8f857798a
<7> 165 Yes INFO: rcu detected stall in sys_unshare (9)
https://syzkaller.appspot.com/bug?extid=872bccd9a68c6ba47718
<8> 116 Yes KASAN: use-after-free Read in qdisc_pkt_len_segs_init
https://syzkaller.appspot.com/bug?extid=83181a31faf9455499c5
<9> 91 Yes INFO: rcu detected stall in rescuer_thread (2)
https://syzkaller.appspot.com/bug?extid=d5f7a5097c24c7c2dbbb
<10> 1366 Yes possible deadlock in hsr_dev_xmit (2)
https://syzkaller.appspot.com/bug?extid=fbf74291c3b7e753b481
---
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-07-25 4:32 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=6a643c61.a2ea2cc8.fbad6.0011.GAE@google.com \
--to=syzbot+list5e1151440ec5d571ba68@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