From: syzbot <syzbot+list4fa12c81c752ac5ed332@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 (Aug 2025)
Date: Mon, 25 Aug 2025 01:44:37 -0700 [thread overview]
Message-ID: <68ac2275.a00a0220.33401d.0402.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 0 were fixed.
In total, 41 issues are still open and 90 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7222 Yes WARNING in call_timer_fn
https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9
<2> 3222 Yes general protection fault in lock_sock_nested
https://syzkaller.appspot.com/bug?extid=d3ccfb78a0dc16ffebe3
<3> 1392 Yes general protection fault in h5_recv
https://syzkaller.appspot.com/bug?extid=b5691bb559396b262064
<4> 749 Yes general protection fault in bcsp_recv
https://syzkaller.appspot.com/bug?extid=4ed6852d4da4606c93da
<5> 651 Yes WARNING in hci_conn_timeout (2)
https://syzkaller.appspot.com/bug?extid=fc4b5b2477d4ca272907
<6> 439 Yes KASAN: slab-use-after-free Read in force_devcd_write
https://syzkaller.appspot.com/bug?extid=bc71245e56f06e3127b7
<7> 349 Yes WARNING: ODEBUG bug in hci_release_dev (2)
https://syzkaller.appspot.com/bug?extid=b170dbf55520ebf5969a
<8> 286 No WARNING in l2cap_chan_del
https://syzkaller.appspot.com/bug?extid=3272785b7a1fc9b510f6
<9> 228 Yes possible deadlock in l2cap_conn_del
https://syzkaller.appspot.com/bug?extid=b71bb48c13bf3fed3692
<10> 152 Yes BUG: sleeping function called from invalid context in lock_sock_nested (3)
https://syzkaller.appspot.com/bug?extid=55cd5225f71c5cff7f6f
---
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-08-25 8:44 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=68ac2275.a00a0220.33401d.0402.GAE@google.com \
--to=syzbot+list4fa12c81c752ac5ed332@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 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.