====================================================== WARNING: possible circular locking dependency detected 6.1.83-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/18709 is trying to acquire lock: ffff88807997f130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1745 [inline] ffff88807997f130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_conn_del+0x104/0x300 net/bluetooth/sco.c:197 but task is already holding lock: ffffffff8e3efe68 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1805 [inline] ffffffff8e3efe68 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb8/0x2a0 net/bluetooth/hci_conn.c:2441 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+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747 hci_connect_cfm include/net/bluetooth/hci_core.h:1790 [inline] hci_remote_features_evt+0x664/0xab0 net/bluetooth/hci_event.c:3778 hci_event_func net/bluetooth/hci_event.c:7514 [inline] hci_event_packet+0xa9d/0x1510 net/bluetooth/hci_event.c:7566 hci_rx_work+0x3cd/0xce0 net/bluetooth/hci_core.c:4130 process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292 worker_thread+0xa47/0x1200 kernel/workqueue.c:2439 kthread+0x28d/0x320 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307 -> #1 (&hdev->lock){+.+.}-{3:3}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747 sco_sock_connect+0x181/0x8f0 net/bluetooth/sco.c:593 __sys_connect_file net/socket.c:2006 [inline] __sys_connect+0x2c9/0x300 net/socket.c:2023 __do_sys_connect net/socket.c:2033 [inline] __se_sys_connect net/socket.c:2030 [inline] __x64_sys_connect+0x76/0x80 net/socket.c:2030 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 lock_sock_nested+0x44/0x100 net/core/sock.c:3484 lock_sock include/net/sock.h:1745 [inline] sco_conn_del+0x104/0x300 net/bluetooth/sco.c:197 hci_disconn_cfm include/net/bluetooth/hci_core.h:1808 [inline] hci_conn_hash_flush+0x10e/0x2a0 net/bluetooth/hci_conn.c:2441 hci_dev_close_sync+0x9a9/0x1020 net/bluetooth/hci_sync.c:5012 hci_dev_do_close net/bluetooth/hci_core.c:554 [inline] hci_unregister_dev+0x1df/0x4d0 net/bluetooth/hci_core.c:2738 vhci_release+0x7f/0xd0 drivers/bluetooth/hci_vhci.c:573 __fput+0x3b7/0x890 fs/file_table.c:320 task_work_run+0x246/0x300 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0xa73/0x26a0 kernel/exit.c:869 do_group_exit+0x202/0x2b0 kernel/exit.c:1019 get_signal+0x16f7/0x17d0 kernel/signal.c:2862 arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871 exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:168 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline] syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297 ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:300 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-executor.0/18709: #0: ffff888062d210b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:552 [inline] #0: ffff888062d210b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1d7/0x4d0 net/bluetooth/hci_core.c:2738 #1: ffff888062d20078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x48d/0x1020 net/bluetooth/hci_sync.c:4999 #2: ffffffff8e3efe68 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1805 [inline] #2: ffffffff8e3efe68 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb8/0x2a0 net/bluetooth/hci_conn.c:2441 stack backtrace: CPU: 1 PID: 18709 Comm: syz-executor.0 Not tainted 6.1.83-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 lock_sock_nested+0x44/0x100 net/core/sock.c:3484 lock_sock include/net/sock.h:1745 [inline] sco_conn_del+0x104/0x300 net/bluetooth/sco.c:197 hci_disconn_cfm include/net/bluetooth/hci_core.h:1808 [inline] hci_conn_hash_flush+0x10e/0x2a0 net/bluetooth/hci_conn.c:2441 hci_dev_close_sync+0x9a9/0x1020 net/bluetooth/hci_sync.c:5012 hci_dev_do_close net/bluetooth/hci_core.c:554 [inline] hci_unregister_dev+0x1df/0x4d0 net/bluetooth/hci_core.c:2738 vhci_release+0x7f/0xd0 drivers/bluetooth/hci_vhci.c:573 __fput+0x3b7/0x890 fs/file_table.c:320 task_work_run+0x246/0x300 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0xa73/0x26a0 kernel/exit.c:869 do_group_exit+0x202/0x2b0 kernel/exit.c:1019 get_signal+0x16f7/0x17d0 kernel/signal.c:2862 arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871 exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:168 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline] syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297 ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:300 RIP: 0033:0x7f197027dda9 Code: Unable to access opcode bytes at 0x7f197027dd7f. RSP: 002b:00007f1970f18078 EFLAGS: 00000246 ORIG_RAX: 0000000000000038 RAX: 0000000000000000 RBX: 00007f19703abf80 RCX: 00007f197027dda9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 00007f19702ca47a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f19703abf80 R15: 00007ffec17c79e8