From: syzbot <syzbot+listd8012b43158f09bd0fcd@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Aug 2026)
Date: Tue, 25 Aug 2026 05:32:43 -0700 [thread overview]
Message-ID: <6a8d8b6b.a5a502ce.31d34.0066.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, 16 new issues were detected and 9 were fixed.
In total, 61 issues are still open and 1772 have already been fixed.
There are also 33 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 6308 Yes unregister_netdevice: waiting for DEV to become free (9)
https://syzkaller.appspot.com/bug?extid=e2af46126e0644cbebdd
<2> 4380 Yes INFO: task hung in synchronize_rcu (4)
https://syzkaller.appspot.com/bug?extid=222aa26d0a5dbc2e84fe
<3> 703 Yes INFO: task hung in tun_chr_close (5)
https://syzkaller.appspot.com/bug?extid=b0ae8f1abf7d891e0426
<4> 501 No possible deadlock in __ipv6_dev_mc_inc
https://syzkaller.appspot.com/bug?extid=afbcf622635e98bf40d2
<5> 454 Yes INFO: task hung in nsim_destroy (4)
https://syzkaller.appspot.com/bug?extid=8141dcbd23a8f857798a
<6> 28 Yes WARNING in dev_shutdown (7)
https://syzkaller.appspot.com/bug?extid=c9ecf60a8adb7629821e
<7> 20 Yes KASAN: slab-use-after-free Read in rxrpc_destroy_all_peers
https://syzkaller.appspot.com/bug?extid=c876adfab6362679008c
<8> 19 Yes KASAN: slab-out-of-bounds Read in __dynamic_pr_debug
https://syzkaller.appspot.com/bug?extid=1e3df0852e82c21ca418
<9> 12 Yes INFO: task hung in inet6_rtm_newaddr (2)
https://syzkaller.appspot.com/bug?extid=101224300649c3eb8af4
<10> 3 Yes BUG: using smp_processor_id() in preemptible code in tx_complete
https://syzkaller.appspot.com/bug?extid=04cd90bb99c6ef81a65d
---
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-08-25 12: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=6a8d8b6b.a5a502ce.31d34.0066.GAE@google.com \
--to=syzbot+listd8012b43158f09bd0fcd@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