On Tue, 30 Nov 2021 at 17:19, syzbot syzbot+a41dfef1d2e04910eb2e@syzkaller.appspotmail.com wrote:

syzbot suspects this issue was fixed by commit:

commit 1bff51ea59a9afb67d2dd78518ab0582a54a472c Author: Wang ShaoBo bobo.shaobowang@huawei.com Date: Wed Sep 1 00:35:37 2021 +0000

Bluetooth: fix use-after-free error in lock_sock_nested()

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=134c881eb00000 start commit: 73b7a6047971 net: dsa: bcm_sf2: support BCM4908's integrat.. git tree: net-next kernel config: https://syzkaller.appspot.com/x/.config?x=9ce34124da4c882b dashboard link: https://syzkaller.appspot.com/bug?extid=a41dfef1d2e04910eb2e syz repro: https://syzkaller.appspot.com/x/repro.syz?x=166ee4cf500000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1337172f500000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: Bluetooth: fix use-after-free error in lock_sock_nested()

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

A use-after-free can lead to other random consequences, and there actually was a KASAN report after the lockdep report in the original report. So w/o a better candidate let's do:

#syz fix: Bluetooth: fix use-after-free error in lock_sock_nested()