From: syzbot <syzbot+list481eec3748b6b7b5a470@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly net report (Mar 2026)
Date: Mon, 23 Mar 2026 02:11:26 -0700 [thread overview]
Message-ID: <69c103be.050a0220.3bf4de.0096.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, 5 new issues were detected and 12 were fixed.
In total, 86 issues are still open and 1711 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 8474 Yes KMSAN: uninit-value in eth_type_trans (2)
https://syzkaller.appspot.com/bug?extid=0901d0cc75c3d716a3a3
<2> 3481 Yes INFO: task hung in linkwatch_event (4)
https://syzkaller.appspot.com/bug?extid=2ba2d70f288cf61174e4
<3> 2911 Yes WARNING in rcu_check_gp_start_stall
https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa
<4> 2768 Yes INFO: task hung in synchronize_rcu (4)
https://syzkaller.appspot.com/bug?extid=222aa26d0a5dbc2e84fe
<5> 2101 Yes KMSAN: uninit-value in bpf_prog_run_generic_xdp
https://syzkaller.appspot.com/bug?extid=0e6ddb1ef80986bdfe64
<6> 1995 Yes INFO: task hung in del_device_store
https://syzkaller.appspot.com/bug?extid=6d10ecc8a97cc10639f9
<7> 1650 Yes INFO: task hung in addrconf_dad_work (5)
https://syzkaller.appspot.com/bug?extid=82ccd564344eeaa5427d
<8> 1201 Yes possible deadlock in hsr_dev_xmit (2)
https://syzkaller.appspot.com/bug?extid=fbf74291c3b7e753b481
<9> 626 Yes INFO: rcu detected stall in tc_modify_qdisc
https://syzkaller.appspot.com/bug?extid=9f78d5c664a8c33f4cce
<10> 609 Yes INFO: task hung in switchdev_deferred_process_work (3)
https://syzkaller.appspot.com/bug?extid=d6bbe0f5705cb8a5aa2b
---
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-03-23 9:11 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=69c103be.050a0220.3bf4de.0096.GAE@google.com \
--to=syzbot+list481eec3748b6b7b5a470@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.