[v6.1] WARNING in hci_recv_frame (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c27210688955 Linux 6.1.173
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=145c56d2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=9331eb2fa6186ef25294
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/92fbc0595a58/disk-c2721068.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0f281a0d62f7/vmlinux-c2721068.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b17a33c5f1fe/bzImage-c2721068.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9331eb...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 8012 at kernel/workqueue.c:1441 __queue_work+0xe2d/0xfb0 kernel/workqueue.c:1441
Modules linked in:
CPU: 0 PID: 8012 Comm: syz.0.1212 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:__queue_work+0xe2d/0xfb0 kernel/workqueue.c:1441
Code: e9 9d fc ff ff 48 8b 0c 24 80 e1 07 80 c1 03 38 c1 0f 8c c7 fc ff ff 48 8b 3c 24 e8 dd 23 7f 00 e9 b9 fc ff ff e8 a3 17 2e 00 <0f> 0b 48 83 c4 60 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 8d 17 2e 00
RSP: 0018:ffffc9000d6ffae8 EFLAGS: 00010083
RAX: ffffffff81546f0d RBX: 0000000000010000 RCX: 0000000000080000
RDX: ffffc9000df9a000 RSI: 0000000000000085 RDI: 0000000000000086
RBP: 0000000000000000 R08: ffff8880781b10c7 R09: 1ffff1100f036218
R10: dffffc0000000000 R11: ffffed100f036219 R12: ffff88805e758000
R13: ffff88805e7581c0 R14: 0000000000000008 R15: ffff888055a5a301
FS: 00007fc84a23a6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc84a239ff8 CR3: 000000007db4f000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
queue_work_on+0x124/0x1f0 kernel/workqueue.c:1548
queue_work include/linux/workqueue.h:512 [inline]
hci_recv_frame+0x528/0x640 net/bluetooth/hci_core.c:2955
vhci_get_user drivers/bluetooth/hci_vhci.c:420 [inline]
vhci_write+0x345/0x460 drivers/bluetooth/hci_vhci.c:516
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x4b1/0xa30 fs/read_write.c:584
ksys_write+0x14c/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc84935d68e
Code: 08 0f 85 a5 a8 ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 80 00 00 00 00 48 83 ec 08
RSP: 002b:00007fc84a239fb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc84a23a6c0 RCX: 00007fc84935d68e
RDX: 0000000000000022 RSI: 0000200000000040 RDI: 00000000000000ca
RBP: 00007fc849432d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc849616128 R14: 00007fc849616090 R15: 00007fffd7605708
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup