[v6.1] WARNING in hci_recv_frame

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: aa4cd140bba5 Linux 6.1.112
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e34b9f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=33931c04473f8585
dashboard link: https://syzkaller.appspot.com/bug?extid=db35545c24f30fb233cb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2a9778339706/disk-aa4cd140.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b568a6da8a9b/vmlinux-aa4cd140.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c56af7eb2c4/bzImage-aa4cd140.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 10210 at kernel/workqueue.c:1441 __queue_work+0xddc/0xf90
Modules linked in:
CPU: 1 PID: 10210 Comm: syz-executor Not tainted 6.1.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__queue_work+0xddc/0xf90 kernel/workqueue.c:1441
Code: 8b 3c 24 e8 a6 a0 88 00 e9 d9 fc ff ff e8 6c 1e 31 00 89 ee 48 c7 c7 80 99 1d 8d e8 1e 6c 0b 03 e9 1e fc ff ff e8 54 1e 31 00 <0f> 0b 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 3e 1e 31 00
RSP: 0018:ffffc900036bf9b8 EFLAGS: 00010093
RAX: ffffffff815990ec RBX: 00000000000b0012 RCX: ffff88802dfd3b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000010000 R08: ffffffff815a7edb R09: ffffed100c1f81a3
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000200
R13: dffffc0000000000 R14: 0000000000000008 R15: ffff88807f1b8000
FS: 0000555564132500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcb231c9030 CR3: 00000000691e3000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
queue_work_on+0x14b/0x250 kernel/workqueue.c:1548
queue_work include/linux/workqueue.h:512 [inline]
hci_recv_frame+0x473/0x5f0 net/bluetooth/hci_core.c:2935
vhci_get_user drivers/bluetooth/hci_vhci.c:420 [inline]
vhci_write+0x31d/0x440 drivers/bluetooth/hci_vhci.c:516
do_iter_write+0x6e6/0xc40 fs/read_write.c:861
vfs_writev fs/read_write.c:934 [inline]
do_writev+0x27b/0x460 fs/read_write.c:977
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fcb2317dc8d
Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 1a 7c 02 00 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 14 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 44 24 08 e8 6e 7c 02 00 48
RSP: 002b:00007ffcc24b6a50 EFLAGS: 00000293 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fcb2317dc8d
RDX: 0000000000000003 RSI: 00007ffcc24b6a90 RDI: 00000000000000ca
RBP: 00005555641324a8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000293 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000009 R15: 0000000000000000
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.