syzbot
possible deadlock in l2cap_chan_connect
Status:
upstream: reported on 2026/09/14 22:12
Reported-by: syzbot+c765b5fd13e1030220e2@syzkaller.appspotmail.com
First crash: 4d04h, last: 23h13m
Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.409/5916 is trying to acquire lock:
ffff88805ff38478 (&hdev->lock){+.+.}-{3:3}, at: l2cap_chan_connect+0xfb/0xe20 net/bluetooth/l2cap_core.c:8205
but task is already holding lock:
ffffffff8d5b37c8 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_open+0x99/0x10c0 net/bluetooth/rfcomm/core.c:425
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (rfcomm_mutex){+.+.}-{3:3}:
__mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
rfcomm_security_cfm+0x95/0x780 net/bluetooth/rfcomm/core.c:2210
hci_auth_cfm include/net/bluetooth/hci_core.h:1543 [inline]
hci_key_refresh_complete_evt+0x44f/0x880 net/bluetooth/hci_event.c:4690
hci_event_packet+0x5d6/0x1310 net/bluetooth/hci_event.c:6525
hci_rx_work+0x255/0xa10 net/bluetooth/hci_core.c:5190
process_one_work+0x867/0xff0 kernel/workqueue.c:2310
worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
-> #1 (hci_cb_list_lock){+.+.}-{3:3}:
__mutex_lock_common+0x1e5/0x2400 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:1504 [inline]
hci_remote_features_evt+0x5d9/0xa10 net/bluetooth/hci_event.c:3367
hci_event_packet+0x600/0x1310 net/bluetooth/hci_event.c:6455
hci_rx_work+0x255/0xa10 net/bluetooth/hci_core.c:5190
process_one_work+0x867/0xff0 kernel/workqueue.c:2310
worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
-> #0 (&hdev->lock){+.+.}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3053 [inline]
check_prevs_add kernel/locking/lockdep.c:3172 [inline]
validate_chain kernel/locking/lockdep.c:3788 [inline]
__lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5625
__mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
l2cap_chan_connect+0xfb/0xe20 net/bluetooth/l2cap_core.c:8205
l2cap_sock_connect+0x5a3/0x770 net/bluetooth/l2cap_sock.c:255
kernel_connect+0x11c/0x180 net/socket.c:3498
rfcomm_session_create net/bluetooth/rfcomm/core.c:807 [inline]
__rfcomm_dlc_open net/bluetooth/rfcomm/core.c:384 [inline]
rfcomm_dlc_open+0x600/0x10c0 net/bluetooth/rfcomm/core.c:427
rfcomm_sock_connect+0x2e9/0x600 net/bluetooth/rfcomm/sock.c:421
__sys_connect_file net/socket.c:1933 [inline]
__sys_connect+0x3cb/0x450 net/socket.c:1950
__do_sys_connect net/socket.c:1960 [inline]
__se_sys_connect net/socket.c:1957 [inline]
__x64_sys_connect+0x76/0x80 net/socket.c:1957
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
other info that might help us debug this:
Chain exists of:
&hdev->lock --> hci_cb_list_lock --> rfcomm_mutex
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(rfcomm_mutex);
lock(hci_cb_list_lock);
lock(rfcomm_mutex);
lock(&hdev->lock);
*** DEADLOCK ***
1 lock held by syz.0.409/5916:
#0: ffffffff8d5b37c8
(rfcomm_mutex
){+.+.}-{3:3}, at: rfcomm_dlc_open+0x99/0x10c0 net/bluetooth/rfcomm/core.c:425
stack backtrace:
CPU: 0 PID: 5916 Comm: syz.0.409 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
check_noncircular+0x296/0x330 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 kernel/locking/lockdep.c:3788 [inline]
__lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5625
__mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
l2cap_chan_connect+0xfb/0xe20 net/bluetooth/l2cap_core.c:8205
l2cap_sock_connect+0x5a3/0x770 net/bluetooth/l2cap_sock.c:255
kernel_connect+0x11c/0x180 net/socket.c:3498
rfcomm_session_create net/bluetooth/rfcomm/core.c:807 [inline]
__rfcomm_dlc_open net/bluetooth/rfcomm/core.c:384 [inline]
rfcomm_dlc_open+0x600/0x10c0 net/bluetooth/rfcomm/core.c:427
rfcomm_sock_connect+0x2e9/0x600 net/bluetooth/rfcomm/sock.c:421
__sys_connect_file net/socket.c:1933 [inline]
__sys_connect+0x3cb/0x450 net/socket.c:1950
__do_sys_connect net/socket.c:1960 [inline]
__se_sys_connect net/socket.c:1957 [inline]
__x64_sys_connect+0x76/0x80 net/socket.c:1957
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f2ef277b159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2ef09d3028 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: ffffffffffffffda RBX: 00007f2ef2a02fa0 RCX: 00007f2ef277b159
RDX: 000000000000000a RSI: 0000200000005dc0 RDI: 0000000000000004
RBP: 00007f2ef281206b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2ef2a03038 R14: 00007f2ef2a02fa0 R15: 00007fffbdb80628
</TASK>
hcon ffff888068de6000 orig refcnt 0
conn ffff88805f9f4800, psm 0x03, dcid 0x0000
chan ffff888060fb1000 orig refcnt 2
hcon ffff888068de6000 orig refcnt 1
hcon ffff888068de6000 orig refcnt 2
chan ffff888060fb1000 BT_BOUND -> BT_CONNECT
chan ffff888060fb1000 state BT_CONNECT timeout 4000
chan ffff888060fb1000 orig refcnt 3
hcon ffff888068de6000
conn ffff88805f9f4800, code 0x02, ident 0x02, len 4
code 0x02
hci2 chan ffff88805fd7f000 flags 0x0002
hci2 nonfrag skb ffff888025e88500 len 16
hci2 orig refcnt 13
sk ffff888060fb0000
ffff88805f56ac00
dlc ffff88805f56ac00 session ffff88801ade6800
session ffff88801ade6800 state 3
dlc ffff88805f56ac00 state 7 timeout 3000
sk ffff88802aa97000
sock ffff888060221800, sk ffff88802aa97000
sock ffff888060221800, sk ffff88802aa97000
sk ffff88802aa97000 state 5 socket ffff888060221800
dlc ffff88805f56ac00 state 7 dlci 42 err 0
dlc ffff88805f56ac00 state 7 dlci 42 err 0 session ffff88801ade6800
dlc ffff88805f56ac00 state 7
dlc ffff88805f56ac00 state 9 err 0
dlc ffff88805f56ac00 refcnt 2 session ffff88801ade6800
session ffff88801ade6800 state 3 timeout 200
sk ffff88802aa97000 state 9 refcnt 2
sk ffff88802aa97000 dlc ffff88805f56ac00
ffff88805f56ac00
* Struck through repros no longer work on HEAD.