From: syzbot <syzbot+list85f939fc7e5f454b1c1f@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 (Feb 2026)
Date: Fri, 06 Feb 2026 06:30:36 -0800 [thread overview]
Message-ID: <6985fb0c.a00a0220.34fa92.002f.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, 2 new issues were detected and 1 were fixed.
In total, 25 issues are still open and 318 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 16793 Yes WARNING in reg_bounds_sanity_check (2)
https://syzkaller.appspot.com/bug?extid=c950cc277150935cc0b5
<2> 2297 Yes WARNING in trace_suspend_resume
https://syzkaller.appspot.com/bug?extid=99d4fec338b62b703891
<3> 102 No INFO: rcu detected stall in sys_sendmmsg (7)
https://syzkaller.appspot.com/bug?extid=53e660acb94e444b9d63
<4> 59 Yes inconsistent lock state in bpf_lru_push_free
https://syzkaller.appspot.com/bug?extid=c69a0a2c816716f1e0d5
<5> 45 No KMSAN: uninit-value in handle_bug
https://syzkaller.appspot.com/bug?extid=ba80855313e6fa65717a
<6> 22 Yes INFO: rcu detected stall in task_numa_work (2)
https://syzkaller.appspot.com/bug?extid=06d48cbf3e767907cec2
<7> 7 Yes KASAN: stack-out-of-bounds Write in __bpf_get_stack
https://syzkaller.appspot.com/bug?extid=d1b7fa1092def3628bd7
<8> 1 Yes INFO: rcu detected stall in vma_merge_new_range (3)
https://syzkaller.appspot.com/bug?extid=316c0070a0341d2661a2
---
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-02-06 14:30 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=6985fb0c.a00a0220.34fa92.002f.GAE@google.com \
--to=syzbot+list85f939fc7e5f454b1c1f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox