[syzbot] [bluetooth?] WARNING in hci_conn_timeout (2)

[syzbot <syzbot+fc4b5b2477d4ca272907@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    f44d154d6e3d Merge tag 'soc-fixes-6.13' of git://git.kerne..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=129d5730580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f
dashboard link: https://syzkaller.appspot.com/bug?extid=fc4b5b2477d4ca272907
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12f282df980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=127e4744580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e8be4151807d/disk-f44d154d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a5f22853d301/vmlinux-f44d154d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d7a4a78964e0/bzImage-f44d154d.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5856 at net/bluetooth/hci_conn.c:567 hci_conn_timeout+0xfb/0x290 net/bluetooth/hci_conn.c:567
Modules linked in:
CPU: 1 UID: 0 PID: 5856 Comm: kworker/u9:7 Not tainted 6.13.0-rc3-syzkaller-00017-gf44d154d6e3d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
Workqueue: hci4 hci_conn_timeout
RIP: 0010:hci_conn_timeout+0xfb/0x290 net/bluetooth/hci_conn.c:567
Code: 4c 89 f7 e8 07 c2 09 00 eb 07 e8 70 55 e5 f6 b0 13 0f b6 f0 4c 89 f7 5b 41 5c 41 5e 41 5f 5d e9 5b b3 fe ff e8 56 55 e5 f6 90 <0f> 0b 90 eb 8f 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 36 ff ff ff 48
RSP: 0018:ffffc90003177b90 EFLAGS: 00010293
RAX: ffffffff8aba1e9a RBX: ffff8880310048e8 RCX: ffff888034bf1e00
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: 00000000ffffffff R08: ffffffff8aba1e03 R09: 1ffff11006200802
R10: dffffc0000000000 R11: ffffed1006200803 R12: dffffc0000000000
R13: ffffffff8168ee96 R14: ffff888031004000 R15: 0000000002400000
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2cfa32a588 CR3: 00000000338ec000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa68/0x1840 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f2/0x390 kernel/kthread.c:389
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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 syzkaller@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 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.

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