From: syzbot <syzbot+listb1e1f17cbdba99a9f9fe@syzkaller.appspotmail.com>
To: fw@strlen.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly netfilter report (Mar 2026)
Date: Tue, 31 Mar 2026 01:07:21 -0700 [thread overview]
Message-ID: <69cb80b9.a70a0220.97f31.0281.GAE@google.com> (raw)
Hello netfilter maintainers/developers,
This is a 31-day syzbot report for the netfilter subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/netfilter
During the period, 2 new issues were detected and 2 were fixed.
In total, 13 issues are still open and 196 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4918 Yes INFO: rcu detected stall in worker_thread (9)
https://syzkaller.appspot.com/bug?extid=225bfad78b079744fd5e
<2> 692 Yes INFO: rcu detected stall in addrconf_rs_timer (6)
https://syzkaller.appspot.com/bug?extid=fecf8bd19c1f78edb255
<3> 325 Yes INFO: rcu detected stall in gc_worker (3)
https://syzkaller.appspot.com/bug?extid=eec403943a2a2455adaa
<4> 68 No INFO: task hung in nfnetlink_rcv_msg (5)
https://syzkaller.appspot.com/bug?extid=c4b20b80ee6a7a2f5012
<5> 11 Yes KMSAN: uninit-value in ip6table_mangle_hook (3)
https://syzkaller.appspot.com/bug?extid=6023ea32e206eef7920a
<6> 6 Yes WARNING in nf_ct_bridge_post
https://syzkaller.appspot.com/bug?extid=a8ba738fe2db6b4bb27f
---
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-31 8:07 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=69cb80b9.a70a0220.97f31.0281.GAE@google.com \
--to=syzbot+listb1e1f17cbdba99a9f9fe@syzkaller.appspotmail.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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