======================================================
WARNING: possible circular locking dependency detected
5.15.113-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor374/3509 is trying to acquire lock:
ffff888022ce2120 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
ffff888022ce2120 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_conn_del+0x104/0x300 net/bluetooth/sco.c:196

but task is already holding lock:
ffffffff8db26de8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1518 [inline]
ffffffff8db26de8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb8/0x210 net/bluetooth/hci_conn.c:1610

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (hci_cb_list_lock){+.+.}-{3:3}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
       __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       hci_connect_cfm include/net/bluetooth/hci_core.h:1503 [inline]
       hci_remote_features_evt+0x6d1/0xb50 net/bluetooth/hci_event.c:3323
       hci_event_packet+0x6da/0x1480 net/bluetooth/hci_event.c:6376
       hci_rx_work+0x240/0x7d0 net/bluetooth/hci_core.c:5153
       process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2307
       worker_thread+0xaca/0x1280 kernel/workqueue.c:2454
       kthread+0x3f6/0x4f0 kernel/kthread.c:319
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298

-> #1 (&hdev->lock){+.+.}-{3:3}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
       __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       sco_sock_connect+0x181/0x8c0 net/bluetooth/sco.c:587
       __sys_connect_file net/socket.c:1899 [inline]
       __sys_connect+0x38b/0x410 net/socket.c:1916
       __do_sys_connect net/socket.c:1926 [inline]
       __se_sys_connect net/socket.c:1923 [inline]
       __x64_sys_connect+0x76/0x80 net/socket.c:1923
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x61/0xcb

-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain+0x1646/0x58b0 kernel/locking/lockdep.c:3787
       __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
       lock_sock_nested+0x44/0x100 net/core/sock.c:3216
       lock_sock include/net/sock.h:1649 [inline]
       sco_conn_del+0x104/0x300 net/bluetooth/sco.c:196
       hci_disconn_cfm include/net/bluetooth/hci_core.h:1521 [inline]
       hci_conn_hash_flush+0x10d/0x210 net/bluetooth/hci_conn.c:1610
       hci_dev_do_close+0x9f6/0x1000 net/bluetooth/hci_core.c:1795
       hci_unregister_dev+0x2a7/0x510 net/bluetooth/hci_core.c:4033
       vhci_release+0x73/0xc0 drivers/bluetooth/hci_vhci.c:342
       __fput+0x3bf/0x890 fs/file_table.c:280
       task_work_run+0x129/0x1a0 kernel/task_work.c:164
       exit_task_work include/linux/task_work.h:32 [inline]
       do_exit+0x6a3/0x2480 kernel/exit.c:872
       do_group_exit+0x144/0x310 kernel/exit.c:994
       __do_sys_exit_group kernel/exit.c:1005 [inline]
       __se_sys_exit_group kernel/exit.c:1003 [inline]
       __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x61/0xcb

other info that might help us debug this:

Chain exists of:
  sk_lock-AF_BLUETOOTH-BTPROTO_SCO --> &hdev->lock --> hci_cb_list_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(hci_cb_list_lock);
                               lock(&hdev->lock);
                               lock(hci_cb_list_lock);
  lock(sk_lock-AF_BLUETOOTH-BTPROTO_SCO);

 *** DEADLOCK ***

3 locks held by syz-executor374/3509:
 #0: ffff88807e750ff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5e/0x1000 net/bluetooth/hci_core.c:1737
 #1: ffff88807e750078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x42c/0x1000 net/bluetooth/hci_core.c:1782
 #2: ffffffff8db26de8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1518 [inline]
 #2: ffffffff8db26de8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb8/0x210 net/bluetooth/hci_conn.c:1610

stack backtrace:
CPU: 0 PID: 3509 Comm: syz-executor374 Not tainted 5.15.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2f8/0x3b0 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain+0x1646/0x58b0 kernel/locking/lockdep.c:3787
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
 lock_sock_nested+0x44/0x100 net/core/sock.c:3216
 lock_sock include/net/sock.h:1649 [inline]
 sco_conn_del+0x104/0x300 net/bluetooth/sco.c:196
 hci_disconn_cfm include/net/bluetooth/hci_core.h:1521 [inline]
 hci_conn_hash_flush+0x10d/0x210 net/bluetooth/hci_conn.c:1610
 hci_dev_do_close+0x9f6/0x1000 net/bluetooth/hci_core.c:1795
 hci_unregister_dev+0x2a7/0x510 net/bluetooth/hci_core.c:4033
 vhci_release+0x73/0xc0 drivers/bluetooth/hci_vhci.c:342
 __fput+0x3bf/0x890 fs/file_table.c:280
 task_work_run+0x129/0x1a0 kernel/task_work.c:164
 exit_task_work include/linux/task_work.h:32 [inline]
 do_exit+0x6a3/0x2480 kernel/exit.c:872
 do_group_exit+0x144/0x310 kernel/exit.c:994
 __do_sys_exit_group kernel/exit.c:1005 [inline]
 __se_sys_exit_group kernel/exit.c:1003 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f43a6394219
Code: Unable to access opcode bytes at RIP 0x7f43a63941ef.
RSP: 002b:00007fffac7d9358 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f43a641e470 RCX: 00007f43a6394219
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000007
RBP: 0000000000000007 R08: ffffffffffffffb8 R09: 000000000000000c
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f43a641e470
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
 </TASK>