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, 53 issues are still open and 63 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 21745 Yes possible deadlock in rfcomm_sk_state_change
https://syzkaller.appspot.com/bug?extid=d7ce59b06b3eb14fd218
<2> 7056 Yes WARNING in hci_conn_del
https://syzkaller.appspot.com/bug?extid=b2545b087a01a7319474
<3> 5110 Yes WARNING in hci_conn_timeout
https://syzkaller.appspot.com/bug?extid=2446dd3cb07277388db6
<4> 2972 Yes WARNING in call_timer_fn
https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9
<5> 2528 Yes KASAN: slab-use-after-free Read in __hci_req_sync
https://syzkaller.appspot.com/bug?extid=27209997e4015fb4702e
<6> 1001 No possible deadlock in __flush_workqueue
https://syzkaller.appspot.com/bug?extid=da0a9c9721e36db712e8
<7> 680 No possible deadlock in touch_wq_lockdep_map
https://syzkaller.appspot.com/bug?extid=91dbdfecdd3287734d8e
<8> 615 Yes general protection fault in skb_release_data (2)
https://syzkaller.appspot.com/bug?extid=ccfa5775bc1bda21ddd1
<9> 243 Yes KASAN: slab-use-after-free Write in sco_sock_timeout
https://syzkaller.appspot.com/bug?extid=4c0d0c4cde787116d465
<10> 185 Yes general protection fault in lock_sock_nested
https://syzkaller.appspot.com/bug?extid=d3ccfb78a0dc16ffebe3
---
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 [email protected].
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.