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, 13 new issues were detected and 0 were fixed. In total, 38 issues are still open and 63 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 19159 Yes possible deadlock in rfcomm_sk_state_change https://syzkaller.appspot.com/bug?extid=d7ce59b06b3eb14fd218 <2> 10784 Yes possible deadlock in rfcomm_dlc_exists https://syzkaller.appspot.com/bug?extid=b69a625d06e8ece26415 <3> 4973 Yes WARNING in hci_conn_timeout https://syzkaller.appspot.com/bug?extid=2446dd3cb07277388db6 <4> 2414 Yes WARNING in call_timer_fn https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9 <5> 307 Yes memory leak in corrupted (2) https://syzkaller.appspot.com/bug?extid=e1c69cadec0f1a078e3d <6> 221 Yes KASAN: slab-use-after-free Write in sco_sock_timeout https://syzkaller.appspot.com/bug?extid=4c0d0c4cde787116d465 <7> 220 Yes WARNING in hci_conn_del https://syzkaller.appspot.com/bug?extid=b2545b087a01a7319474 <8> 62 Yes general protection fault in lock_sock_nested https://syzkaller.appspot.com/bug?extid=d3ccfb78a0dc16ffebe3 <9> 56 Yes KASAN: slab-use-after-free Write in sco_conn_del https://syzkaller.appspot.com/bug?extid=6b9277cad941daf126a2 <10> 52 No possible deadlock in __flush_workqueue https://syzkaller.appspot.com/bug?extid=da0a9c9721e36db712e8 --- 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@xxxxxxxxxxxxxxxx. 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.
