From: syzbot <syzbot+list84175158135809b979c6@syzkaller.appspotmail.com>
To: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly bluetooth report (Sep 2025)
Date: Wed, 24 Sep 2025 05:39:34 -0700 [thread overview]
Message-ID: <68d3e686.a70a0220.4f78.0023.GAE@google.com> (raw)
Hello bluetooth maintainers/developers,
This is a 31-day syzbot report for the bluetooth subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/bluetooth
During the period, 2 new issues were detected and 1 were fixed.
In total, 38 issues are still open and 91 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 43283 Yes KASAN: slab-use-after-free Read in l2cap_unregister_user
https://syzkaller.appspot.com/bug?extid=14b6d57fb728e27ce23c
<2> 7364 Yes WARNING in call_timer_fn
https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9
<3> 3411 Yes general protection fault in lock_sock_nested
https://syzkaller.appspot.com/bug?extid=d3ccfb78a0dc16ffebe3
<4> 1710 Yes general protection fault in h5_recv
https://syzkaller.appspot.com/bug?extid=b5691bb559396b262064
<5> 719 Yes WARNING in hci_conn_timeout (2)
https://syzkaller.appspot.com/bug?extid=fc4b5b2477d4ca272907
<6> 360 Yes WARNING: ODEBUG bug in hci_release_dev (2)
https://syzkaller.appspot.com/bug?extid=b170dbf55520ebf5969a
<7> 304 No WARNING in l2cap_chan_del
https://syzkaller.appspot.com/bug?extid=3272785b7a1fc9b510f6
<8> 274 Yes possible deadlock in l2cap_conn_del
https://syzkaller.appspot.com/bug?extid=b71bb48c13bf3fed3692
<9> 139 Yes KASAN: slab-use-after-free Read in l2cap_recv_frame
https://syzkaller.appspot.com/bug?extid=5c915dc5dd417b83b348
<10> 113 No BUG: corrupted list in hci_cmd_sync_dequeue_once
https://syzkaller.appspot.com/bug?extid=5250d87dea2afdb718a5
---
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-09-24 12:39 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=68d3e686.a70a0220.4f78.0023.GAE@google.com \
--to=syzbot+list84175158135809b979c6@syzkaller.appspotmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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