====================================================== WARNING: possible circular locking dependency detected 5.15.156-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/5202 is trying to acquire lock: ffff88801a216120 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1668 [inline] ffff88801a216120 (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: ffffffff8db30628 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1522 [inline] ffffffff8db30628 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb8/0x220 net/bluetooth/hci_conn.c:1622 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:5623 __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:1507 [inline] hci_remote_features_evt+0x52f/0xb50 net/bluetooth/hci_event.c:3352 hci_event_packet+0x6fe/0x1550 net/bluetooth/hci_event.c:6421 hci_rx_work+0x232/0x990 net/bluetooth/hci_core.c:5156 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457 kthread+0x3f6/0x4f0 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300 -> #1 (&hdev->lock){+.+.}-{3:3}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __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/0x8e0 net/bluetooth/sco.c:587 __sys_connect_file net/socket.c:1918 [inline] __sys_connect+0x38b/0x410 net/socket.c:1935 __do_sys_connect net/socket.c:1945 [inline] __se_sys_connect net/socket.c:1942 [inline] __x64_sys_connect+0x76/0x80 net/socket.c:1942 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #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+0x1649/0x5930 kernel/locking/lockdep.c:3788 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 lock_sock_nested+0x44/0x100 net/core/sock.c:3250 lock_sock include/net/sock.h:1668 [inline] sco_conn_del+0x104/0x300 net/bluetooth/sco.c:196 hci_disconn_cfm include/net/bluetooth/hci_core.h:1525 [inline] hci_conn_hash_flush+0x10d/0x220 net/bluetooth/hci_conn.c:1622 hci_dev_do_close+0x9f6/0x1070 net/bluetooth/hci_core.c:1795 hci_unregister_dev+0x2a7/0x550 net/bluetooth/hci_core.c:4036 vhci_release+0x73/0xc0 drivers/bluetooth/hci_vhci.c:345 __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 get_signal+0xc66/0x14e0 kernel/signal.c:2889 arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867 handle_signal_work kernel/entry/common.c:154 [inline] exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:178 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline] syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307 ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:293 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.1/5202: #0: ffff8880790c0ff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x63/0x1070 net/bluetooth/hci_core.c:1737 #1: ffff8880790c0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x431/0x1070 net/bluetooth/hci_core.c:1782 #2: ffffffff8db30628 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1522 [inline] #2: ffffffff8db30628 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb8/0x220 net/bluetooth/hci_conn.c:1622 stack backtrace: CPU: 1 PID: 5202 Comm: syz-executor.1 Not tainted 5.15.156-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/0x2d0 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+0x1649/0x5930 kernel/locking/lockdep.c:3788 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 lock_sock_nested+0x44/0x100 net/core/sock.c:3250 lock_sock include/net/sock.h:1668 [inline] sco_conn_del+0x104/0x300 net/bluetooth/sco.c:196 hci_disconn_cfm include/net/bluetooth/hci_core.h:1525 [inline] hci_conn_hash_flush+0x10d/0x220 net/bluetooth/hci_conn.c:1622 hci_dev_do_close+0x9f6/0x1070 net/bluetooth/hci_core.c:1795 hci_unregister_dev+0x2a7/0x550 net/bluetooth/hci_core.c:4036 vhci_release+0x73/0xc0 drivers/bluetooth/hci_vhci.c:345 __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 get_signal+0xc66/0x14e0 kernel/signal.c:2889 arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867 handle_signal_work kernel/entry/common.c:154 [inline] exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:178 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline] syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307 ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:293 RIP: 0033:0x7f1e8b732ea9 Code: Unable to access opcode bytes at RIP 0x7f1e8b732e7f. RSP: 002b:00007f1e89ca5078 EFLAGS: 00000246 ORIG_RAX: 0000000000000038 RAX: 0000000000000000 RBX: 00007f1e8b860f80 RCX: 00007f1e8b732ea9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 00007f1e8b77f4a4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f1e8b860f80 R15: 00007fffaeddf718