From: syzbot <syzbot+liste2c3cfac8f434c3230cd@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly bpf report (Mar 2026)
Date: Mon, 09 Mar 2026 16:06:31 -0700 [thread overview]
Message-ID: <69af5277.a00a0220.b130.0019.GAE@google.com> (raw)
Hello bpf maintainers/developers,
This is a 31-day syzbot report for the bpf subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/bpf
During the period, 3 new issues were detected and 5 were fixed.
In total, 25 issues are still open and 323 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 19578 Yes WARNING in reg_bounds_sanity_check (2)
https://syzkaller.appspot.com/bug?extid=c950cc277150935cc0b5
<2> 2433 Yes WARNING in trace_suspend_resume
https://syzkaller.appspot.com/bug?extid=99d4fec338b62b703891
<3> 241 No KMSAN: uninit-value in handle_bug
https://syzkaller.appspot.com/bug?extid=ba80855313e6fa65717a
<4> 216 Yes inconsistent lock state in bpf_lru_push_free
https://syzkaller.appspot.com/bug?extid=c69a0a2c816716f1e0d5
<5> 102 No INFO: task hung in dev_map_free (3)
https://syzkaller.appspot.com/bug?extid=9bb2e1829da8582dcffa
<6> 44 Yes KASAN: slab-use-after-free Read in bpf_trace_run2 (3)
https://syzkaller.appspot.com/bug?extid=59701a78e84b0bccfe1b
<7> 1 Yes possible deadlock in bpf_lru_push_free (2)
https://syzkaller.appspot.com/bug?extid=18b26edb69b2e19f3b33
---
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-09 23:06 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=69af5277.a00a0220.b130.0019.GAE@google.com \
--to=syzbot+liste2c3cfac8f434c3230cd@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@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.