[v6.6] WARNING in hci_conn_timeout

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10a4b70c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=e6c889790f3159fa29e2
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5776 at net/bluetooth/hci_conn.c:568 hci_conn_timeout+0xf9/0x290 net/bluetooth/hci_conn.c:568
Modules linked in:
CPU: 1 PID: 5776 Comm: kworker/u5:3 Not tainted 6.6.94-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: hci4 hci_conn_timeout
RIP: 0010:hci_conn_timeout+0xf9/0x290 net/bluetooth/hci_conn.c:568
Code: f8 48 89 df e8 c8 b7 08 00 eb 07 e8 b1 11 1c f8 b0 13 0f b6 f0 48 89 df 5b 41 5c 41 5e 41 5f 5d e9 ec e0 fe ff e8 97 11 1c f8 <0f> 0b eb 8e 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 38 ff ff ff 4c
RSP: 0018:ffffc900045e7b90 EFLAGS: 00010293
RAX: ffffffff89698439 RBX: ffff8880788c6000 RCX: ffff8880233a0000
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: 00000000ffffffff R08: ffff8880788c6013 R09: 1ffff1100f118c02
R10: dffffc0000000000 R11: ffffed100f118c03 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff8880788c6350 R15: ffff8880788c6010
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000006a6d8000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1530f70c580000

kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=e6c889790f3159fa29e2
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13003182580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16a19b70580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/659a71df6826/mount_1.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=14574f0c580000)

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

------------[ cut here ]------------

WARNING: CPU: 1 PID: 5790 at net/bluetooth/hci_conn.c:568 hci_conn_timeout+0xf9/0x290 net/bluetooth/hci_conn.c:568
Modules linked in:
CPU: 1 PID: 5790 Comm: kworker/u5:3 Not tainted 6.6.94-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025

Workqueue: hci3 hci_conn_timeout

RIP: 0010:hci_conn_timeout+0xf9/0x290 net/bluetooth/hci_conn.c:568
Code: f8 48 89 df e8 c8 b7 08 00 eb 07 e8 b1 11 1c f8 b0 13 0f b6 f0 48 89 df 5b 41 5c 41 5e 41 5f 5d e9 ec e0 fe ff e8 97 11 1c f8 <0f> 0b eb 8e 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 38 ff ff ff 4c

RSP: 0018:ffffc900046afb90 EFLAGS: 00010293
RAX: ffffffff89698439 RBX: ffff88807ddde000 RCX: ffff888079918000

RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000

RBP: 00000000ffffffff R08: ffff88807ddde013 R09: 1ffff1100fbbbc02
R10: dffffc0000000000 R11: ffffed100fbbbc03 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88807ddde350 R15: ffff88807ddde010

FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f6ff43a7094 CR3: 000000000cb30000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>


---

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.