From: syzbot <syzbot+list6386fc8218378445ebcd@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 (Jan 2025)
Date: Fri, 17 Jan 2025 02:35:27 -0800 [thread overview]
Message-ID: <678a326f.050a0220.20d369.0059.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, 10 new issues were detected and 0 were fixed.
In total, 59 issues are still open and 75 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 22244 Yes KASAN: slab-use-after-free Read in l2cap_unregister_user
https://syzkaller.appspot.com/bug?extid=14b6d57fb728e27ce23c
<2> 5541 Yes WARNING in call_timer_fn
https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9
<3> 719 Yes general protection fault in lock_sock_nested
https://syzkaller.appspot.com/bug?extid=d3ccfb78a0dc16ffebe3
<4> 698 Yes general protection fault in skb_release_data (2)
https://syzkaller.appspot.com/bug?extid=ccfa5775bc1bda21ddd1
<5> 157 Yes WARNING in hci_conn_timeout (2)
https://syzkaller.appspot.com/bug?extid=fc4b5b2477d4ca272907
<6> 129 Yes WARNING: ODEBUG bug in hci_release_dev (2)
https://syzkaller.appspot.com/bug?extid=b170dbf55520ebf5969a
<7> 110 Yes KASAN: slab-use-after-free Read in force_devcd_write
https://syzkaller.appspot.com/bug?extid=bc71245e56f06e3127b7
<8> 106 No WARNING in l2cap_chan_del
https://syzkaller.appspot.com/bug?extid=3272785b7a1fc9b510f6
<9> 105 Yes BUG: sleeping function called from invalid context in lock_sock_nested (3)
https://syzkaller.appspot.com/bug?extid=55cd5225f71c5cff7f6f
<10> 63 No KASAN: slab-use-after-free Read in skb_queue_purge_reason (2)
https://syzkaller.appspot.com/bug?extid=683f8cb11b94b1824c77
---
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-01-17 10:35 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=678a326f.050a0220.20d369.0059.GAE@google.com \
--to=syzbot+list6386fc8218378445ebcd@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.