From: syzbot <syzbot+list9c475ae69cc5384cb852@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 (Jun 2026)
Date: Tue, 02 Jun 2026 13:32:26 -0700 [thread overview]
Message-ID: <6a1f3dda.7b89b7e1.205e57.0007.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, 4 new issues were detected and 0 were fixed.
In total, 27 issues are still open and 102 have already been fixed.
There are also 8 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 9301 Yes WARNING in call_timer_fn
https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9
<2> 564 Yes WARNING: ODEBUG bug in hci_release_dev (2)
https://syzkaller.appspot.com/bug?extid=b170dbf55520ebf5969a
<3> 367 No WARNING in l2cap_chan_del
https://syzkaller.appspot.com/bug?extid=3272785b7a1fc9b510f6
<4> 345 Yes KASAN: wild-memory-access Read in l2cap_connect_cfm
https://syzkaller.appspot.com/bug?extid=0e4ebcc970728e056324
<5> 203 Yes KASAN: slab-use-after-free Read in l2cap_sock_new_connection_cb
https://syzkaller.appspot.com/bug?extid=cdae834448ec8c3602fe
<6> 111 Yes INFO: task hung in hci_cmd_sync_clear (3)
https://syzkaller.appspot.com/bug?extid=217e3f1283cafe80586e
<7> 97 Yes KASAN: slab-use-after-free Read in l2cap_sock_ready_cb (2)
https://syzkaller.appspot.com/bug?extid=9265e754091c2d27ea29
<8> 33 No WARNING: held lock freed in bt_accept_dequeue
https://syzkaller.appspot.com/bug?extid=4c5f0c6f8cc60159bdbf
<9> 165 Yes KASAN: slab-use-after-free Read in bt_accept_unlink
https://syzkaller.appspot.com/bug?extid=a1595e656a83ea5b78eb
<10> 91 Yes general protection fault in l2cap_chan_timeout (3)
https://syzkaller.appspot.com/bug?extid=f0908ddc8b64b86e81f2
---
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-06-02 20:32 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=6a1f3dda.7b89b7e1.205e57.0007.GAE@google.com \
--to=syzbot+list9c475ae69cc5384cb852@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