From: syzbot <syzbot+listb55ee1602b5d90b0989f@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 (Nov 2024)
Date: Fri, 15 Nov 2024 06:41:29 -0800 [thread overview]
Message-ID: <67375d99.050a0220.bb738.0001.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, 6 new issues were detected and 0 were fixed.
In total, 48 issues are still open and 72 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 695 Yes general protection fault in skb_release_data (2)
https://syzkaller.appspot.com/bug?extid=ccfa5775bc1bda21ddd1
<2> 452 Yes general protection fault in lock_sock_nested
https://syzkaller.appspot.com/bug?extid=d3ccfb78a0dc16ffebe3
<3> 346 Yes BUG: sleeping function called from invalid context in hci_le_create_big_complete_evt
https://syzkaller.appspot.com/bug?extid=2fb0835e0c9cefc34614
<4> 141 Yes KASAN: slab-use-after-free Read in set_powered_sync
https://syzkaller.appspot.com/bug?extid=03d6270b6425df1605bf
<5> 76 Yes BUG: sleeping function called from invalid context in lock_sock_nested (3)
https://syzkaller.appspot.com/bug?extid=55cd5225f71c5cff7f6f
<6> 52 Yes WARNING: ODEBUG bug in put_device
https://syzkaller.appspot.com/bug?extid=a9290936c6e87b3dc3c2
<7> 50 No KASAN: slab-use-after-free Read in skb_queue_purge_reason (2)
https://syzkaller.appspot.com/bug?extid=683f8cb11b94b1824c77
<8> 42 No WARNING in l2cap_chan_del
https://syzkaller.appspot.com/bug?extid=3272785b7a1fc9b510f6
<9> 33 Yes possible deadlock in mgmt_set_connectable_complete
https://syzkaller.appspot.com/bug?extid=b1752fcfa8658bb8984a
<10> 9 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:[~2024-11-15 14:41 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=67375d99.050a0220.bb738.0001.GAE@google.com \
--to=syzbot+listb55ee1602b5d90b0989f@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.