possible deadlock in rfcomm_run

Status: upstream: reported on 2026/10/02 06:15
Subsystems: bluetooth
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+0adf2aef8ca78b84c4df@syzkaller.appspotmail.com
First crash: 50d, last: 23h19m
▶ ▼ ✨ AI Jobs (3)
ID Workflow Result Correct Bug Created Started Finished Revision
791d1e4f repro-c 💥 possible deadlock in rfcomm_run 2026/10/03 04:25 2026/10/03 04:25 2026/10/03 07:14 57bbd979
4df323a9 repro-c 💥 possible deadlock in rfcomm_run 2026/10/01 06:13 2026/10/01 06:13 2026/10/01 10:33 38f7f0d1
f89be1b1 assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ✅ VMHostTrigger: ❌ ❓ possible deadlock in rfcomm_run 2026/09/30 03:02 2026/09/30 03:02 2026/09/30 03:08 69537153
▶ ▼ Discussions (3)
Title Replies (including bot) Last reply
[syzbot] Monthly bluetooth report (Nov 2026) 0 (1) 2026/11/06 04:33
[syzbot] Monthly bluetooth report (Oct 2026) 0 (1) 2026/10/05 20:33
[syzbot] [bluetooth?] possible deadlock in rfcomm_run 0 (1) 2026/10/02 06:15
▶ ▼ Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in rfcomm_run 4 1 17d 17d 0/2 upstream: reported on 2026/10/31 14:30

Sample crash report:
kobject: 'hci3' (ffff8880af485538): kobject_cleanup, parent 0000000000000000
kobject: 'hci3' (ffff8880af485538): calling ktype release
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     Y
------------------------------------------------------
krfcommd/3208 is trying to acquire lock:
ffff8880532be948 ((wq_completion)hci3#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x9c/0x1c0 kernel/workqueue.c:4272

but task is already holding lock:
ffffffff921ce680 (rfcomm_mutex){+.+.}-{4:4}, at: rfcomm_process_sessions net/bluetooth/rfcomm/core.c:2150 [inline]
ffffffff921ce680 (rfcomm_mutex){+.+.}-{4:4}, at: rfcomm_run+0x30b/0x5560 net/bluetooth/rfcomm/core.c:2259

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (rfcomm_mutex){+.+.}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19f/0x1c10 kernel/locking/mutex.c:821
       rfcomm_security_cfm+0x3f/0x4b0 net/bluetooth/rfcomm/core.c:2277
       hci_auth_cfm include/net/bluetooth/hci_core.h:2250 [inline]
       hci_auth_complete_evt+0x811/0x1180 net/bluetooth/hci_event.c:3644
       hci_event_func net/bluetooth/hci_event.c:8039 [inline]
       hci_event_packet+0x8e9/0xcd0 net/bluetooth/hci_event.c:8090
       hci_rx_work+0x6ea/0x10c0 net/bluetooth/hci_core.c:4124
       process_one_work+0xac7/0x1b10 kernel/workqueue.c:3495
       process_scheduled_works kernel/workqueue.c:3578 [inline]
       worker_thread+0x5ef/0xe50 kernel/workqueue.c:3659
       kthread+0x373/0x450 kernel/kthread.c:436
       ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #3 (hci_cb_list_lock){+.+.}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19f/0x1c10 kernel/locking/mutex.c:821
       hci_connect_cfm include/net/bluetooth/hci_core.h:2211 [inline]
       hci_remote_features_evt+0x485/0x9b0 net/bluetooth/hci_event.c:3901
       hci_event_func net/bluetooth/hci_event.c:8039 [inline]
       hci_event_packet+0x8e9/0xcd0 net/bluetooth/hci_event.c:8090
       hci_rx_work+0x6ea/0x10c0 net/bluetooth/hci_core.c:4124
       process_one_work+0xac7/0x1b10 kernel/workqueue.c:3495
       process_scheduled_works kernel/workqueue.c:3578 [inline]
       worker_thread+0x5ef/0xe50 kernel/workqueue.c:3659
       kthread+0x373/0x450 kernel/kthread.c:436
       ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #2 (&hdev->lock){+.+.}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x19f/0x1c10 kernel/locking/mutex.c:821
       hci_send_cmd_sync net/bluetooth/hci_core.c:4163 [inline]
       hci_cmd_work+0x1be/0x990 net/bluetooth/hci_core.c:4212
       process_one_work+0xac7/0x1b10 kernel/workqueue.c:3495
       process_scheduled_works kernel/workqueue.c:3578 [inline]
       worker_thread+0x5ef/0xe50 kernel/workqueue.c:3659
       kthread+0x373/0x450 kernel/kthread.c:436
       ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #1 ((work_completion)(&hdev->cmd_work)){+.+.}-{0:0}:
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       process_one_work+0xa32/0x1b10 kernel/workqueue.c:3471
       process_scheduled_works kernel/workqueue.c:3578 [inline]
       worker_thread+0x5ef/0xe50 kernel/workqueue.c:3659
       kthread+0x373/0x450 kernel/kthread.c:436
       ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #0 ((wq_completion)hci3#2){+.+.}-{0:0}:
       check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3209
       check_prevs_add kernel/locking/lockdep.c:3328 [inline]
       validate_chain kernel/locking/lockdep.c:3952 [inline]
       __lock_acquire+0x1528/0x1f40 kernel/locking/lockdep.c:5288
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       touch_wq_lockdep_map+0xad/0x1c0 kernel/workqueue.c:4272
       __flush_workqueue+0x131/0x1200 kernel/workqueue.c:4314
       drain_workqueue+0x175/0x3c0 kernel/workqueue.c:4478
       destroy_workqueue+0xc1/0x9f0 kernel/workqueue.c:6372
       hci_release_dev+0x116/0x630 net/bluetooth/hci_core.c:2728
       bt_host_release+0x6b/0xb0 net/bluetooth/hci_sysfs.c:100
       device_release+0xd2/0x270 drivers/base/core.c:2640
       kobject_cleanup lib/kobject.c:689 [inline]
       kobject_release lib/kobject.c:720 [inline]
       kref_put include/linux/kref.h:65 [inline]
       kobject_put+0x1f7/0x640 lib/kobject.c:737
       put_device+0x1f/0x30 drivers/base/core.c:3884
       device_release+0xd2/0x270 drivers/base/core.c:2640
       kobject_cleanup lib/kobject.c:689 [inline]
       kobject_release lib/kobject.c:720 [inline]
       kref_put include/linux/kref.h:65 [inline]
       kobject_put+0x1f7/0x640 lib/kobject.c:737
       put_device+0x1f/0x30 drivers/base/core.c:3884
       hci_conn_put include/net/bluetooth/hci_core.h:1737 [inline]
       l2cap_conn_free net/bluetooth/l2cap_core.c:1960 [inline]
       kref_put include/linux/kref.h:65 [inline]
       l2cap_conn_put net/bluetooth/l2cap_core.c:1973 [inline]
       l2cap_chan_destroy net/bluetooth/l2cap_core.c:522 [inline]
       kref_put include/linux/kref.h:65 [inline]
       l2cap_chan_put+0x352/0x3f0 net/bluetooth/l2cap_core.c:549
       l2cap_sock_release+0x1db/0x280 net/bluetooth/l2cap_sock.c:1540
       __sock_release net/socket.c:735 [inline]
       sock_release+0x91/0x1c0 net/socket.c:763
       rfcomm_session_del.isra.0+0x16b/0x250 net/bluetooth/rfcomm/core.c:782
       rfcomm_process_rx net/bluetooth/rfcomm/core.c:2084 [inline]
       rfcomm_process_sessions net/bluetooth/rfcomm/core.c:2169 [inline]
       rfcomm_run+0x6f6/0x5560 net/bluetooth/rfcomm/core.c:2259
       kthread+0x373/0x450 kernel/kthread.c:436
       ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

other info that might help us debug this:

Chain exists of:
  (wq_completion)hci3#2 --> hci_cb_list_lock --> rfcomm_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(rfcomm_mutex);
                               lock(hci_cb_list_lock);
                               lock(rfcomm_mutex);
  lock((wq_completion)hci3#2);

 *** DEADLOCK ***

locks held by krfcommd/3208: 1, last CPU#0:
 #0: ffffffff921ce680 (rfcomm_mutex){+.+.}-{4:4}, at: rfcomm_process_sessions net/bluetooth/rfcomm/core.c:2150 [inline]
 #0: ffffffff921ce680 (rfcomm_mutex){+.+.}-{4:4}, at: rfcomm_run+0x30b/0x5560 net/bluetooth/rfcomm/core.c:2259

stack backtrace:
CPU: 0 UID: 0 PID: 3208 Comm: krfcommd Tainted: G             L     Y syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP, [Y]=FORCED_BIND
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/15/2026
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 print_circular_bug.cold+0x178/0x1be kernel/locking/lockdep.c:2087
 check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2219
 check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3209
 check_prevs_add kernel/locking/lockdep.c:3328 [inline]
 validate_chain kernel/locking/lockdep.c:3952 [inline]
 __lock_acquire+0x1528/0x1f40 kernel/locking/lockdep.c:5288
 lock_acquire kernel/locking/lockdep.c:5942 [inline]
 lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
 touch_wq_lockdep_map+0xad/0x1c0 kernel/workqueue.c:4272
 __flush_workqueue+0x131/0x1200 kernel/workqueue.c:4314
 drain_workqueue+0x175/0x3c0 kernel/workqueue.c:4478
 destroy_workqueue+0xc1/0x9f0 kernel/workqueue.c:6372
 hci_release_dev+0x116/0x630 net/bluetooth/hci_core.c:2728
 bt_host_release+0x6b/0xb0 net/bluetooth/hci_sysfs.c:100
 device_release+0xd2/0x270 drivers/base/core.c:2640
 kobject_cleanup lib/kobject.c:689 [inline]
 kobject_release lib/kobject.c:720 [inline]
 kref_put include/linux/kref.h:65 [inline]
 kobject_put+0x1f7/0x640 lib/kobject.c:737
 put_device+0x1f/0x30 drivers/base/core.c:3884
 device_release+0xd2/0x270 drivers/base/core.c:2640
 kobject_cleanup lib/kobject.c:689 [inline]
 kobject_release lib/kobject.c:720 [inline]
 kref_put include/linux/kref.h:65 [inline]
 kobject_put+0x1f7/0x640 lib/kobject.c:737
 put_device+0x1f/0x30 drivers/base/core.c:3884
 hci_conn_put include/net/bluetooth/hci_core.h:1737 [inline]
 l2cap_conn_free net/bluetooth/l2cap_core.c:1960 [inline]
 kref_put include/linux/kref.h:65 [inline]
 l2cap_conn_put net/bluetooth/l2cap_core.c:1973 [inline]
 l2cap_chan_destroy net/bluetooth/l2cap_core.c:522 [inline]
 kref_put include/linux/kref.h:65 [inline]
 l2cap_chan_put+0x352/0x3f0 net/bluetooth/l2cap_core.c:549
 l2cap_sock_release+0x1db/0x280 net/bluetooth/l2cap_sock.c:1540
 __sock_release net/socket.c:735 [inline]
 sock_release+0x91/0x1c0 net/socket.c:763
 rfcomm_session_del.isra.0+0x16b/0x250 net/bluetooth/rfcomm/core.c:782
 rfcomm_process_rx net/bluetooth/rfcomm/core.c:2084 [inline]
 rfcomm_process_sessions net/bluetooth/rfcomm/core.c:2169 [inline]
 rfcomm_run+0x6f6/0x5560 net/bluetooth/rfcomm/core.c:2259
 kthread+0x373/0x450 kernel/kthread.c:436
 ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (22):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/30 16:26 upstream d89e1d186ec9 b498adee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_run
2026/10/30 03:00 upstream 4dd16e31135e b498adee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_run
2026/10/23 21:28 upstream 734bef548a96 d566bfda .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_run
2026/10/23 06:18 upstream 2a08195e4db5 4ba27f85 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_run
2026/10/03 19:47 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_run
2026/11/16 22:27 upstream 141b164bbe18 a3e64cfc .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_run
2026/11/10 03:08 upstream 7475ea8b5861 bf7e1705 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_run
2026/10/24 23:59 upstream 5b0764a53235 1d9ca40b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_run
2026/10/19 10:18 upstream c03c1a14507d 432c0077 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_run
2026/10/12 03:12 upstream b88c841d1164 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_run
2026/10/10 13:55 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_run
2026/10/09 21:36 upstream af32da41b032 549ef7e3 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_run
2026/09/28 06:06 upstream d266640c6c76 a3c7249d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_run
2026/11/13 17:32 upstream 7e1392a42ea2 0dd86ee6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_run
2026/11/08 21:55 upstream fa4ad798f6f6 5cecaf1f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_run
2026/10/24 14:40 upstream 4da9dedf3fc5 1d9ca40b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_run
2026/11/07 19:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 58c1eb84e977 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_run
2026/10/29 09:17 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7a19f0cc94ad b1d00f76 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_run
2026/10/25 10:18 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7a19f0cc94ad 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_run
2026/10/23 12:49 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7a19f0cc94ad d566bfda .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_run
2026/10/22 04:57 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7a19f0cc94ad 61c200c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_run
2026/10/19 12:55 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7a19f0cc94ad 432c0077 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_run
* Struck through repros no longer work on HEAD.