From: syzbot <syzbot+list9b8f8e5b91eb4f6d281c@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 (Nov 2025)
Date: Wed, 05 Nov 2025 00:25:27 -0800 [thread overview]
Message-ID: <690b09f7.050a0220.baf87.000c.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 1 were fixed.
In total, 21 issues are still open and 312 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 10888 Yes KASAN: invalid-access Write in do_bad_area
https://syzkaller.appspot.com/bug?extid=997752115a851cb0cf36
<2> 97 No INFO: task hung in dev_map_free (3)
https://syzkaller.appspot.com/bug?extid=9bb2e1829da8582dcffa
<3> 21 No KCSAN: data-race in __htab_map_lookup_elem / bpf_lru_pop_free
https://syzkaller.appspot.com/bug?extid=ad4661d6ca888ce7fe11
<4> 12 Yes INFO: rcu detected stall in sys_close (7)
https://syzkaller.appspot.com/bug?extid=393022c13d02e1f680e3
<5> 5 Yes INFO: rcu detected stall in vm_area_alloc (6)
https://syzkaller.appspot.com/bug?extid=2ddfdc64a6b68a324ae2
<6> 2 Yes possible deadlock in down_trylock (3)
https://syzkaller.appspot.com/bug?extid=c3740bc819eb55460ec3
---
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:[~2025-11-05 8:25 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=690b09f7.050a0220.baf87.000c.GAE@google.com \
--to=syzbot+list9b8f8e5b91eb4f6d281c@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