[v5.15] WARNING in process_one_work (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: aabd761612db Linux 5.15.215
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12f01949580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link: https://syzkaller.appspot.com/bug?extid=cfd70907b3e618414560
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5180d63e623b/disk-aabd7616.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/97c68abdfd0f/vmlinux-aabd7616.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e341dd608cb3/bzImage-aabd7616.xz

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

Bluetooth: hci5: command 0x0406 tx timeout
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7147 at kernel/workqueue.c:1453 __queue_work+0xb46/0xc80 kernel/workqueue.c:1453
Modules linked in:
CPU: 0 PID: 7147 Comm: kworker/0:25 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: events hci_cmd_timeout
RIP: 0010:__queue_work+0xb46/0xc80 kernel/workqueue.c:1453
Code: e9 09 fd ff ff 49 8d 4f 5c 80 e1 07 80 c1 03 38 c1 0f 8c 29 fd ff ff 49 8d 7f 5c e8 14 3d 70 00 e9 1b fd ff ff e8 5a 1a 2b 00 <0f> 0b 48 83 c4 48 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 44 1a 2b 00
RSP: 0018:ffffc9000394fae0 EFLAGS: 00010093
RAX: ffffffff814de256 RBX: dffffc0000000000 RCX: ffff88802bc05940
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: 0000000000010000 R08: ffff888057130f37 R09: 1ffff1100ae261e6
R10: dffffc0000000000 R11: ffffed100ae261e7 R12: 0000000000000008
R13: 1ffff92000729f70 R14: ffff88807878f1c0 R15: ffff88807878f000
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa1a1b88a08 CR3: 000000002a76c000 CR4: 00000000003506f0
DR0: 0000200000000300 DR1: 0000200000000300 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
queue_work_on+0x124/0x1f0 kernel/workqueue.c:1559
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
</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