[moderation] [bluetooth?] WARNING: ODEBUG bug in hci_abort_conn_sync

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5d2f53532ecc Merge tag 'spi-fix-v6.6-rc2' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12d3d87a680000
kernel config: https://syzkaller.appspot.com/x/.config?x=e4ca82a1bedd37e4
dashboard link: https://syzkaller.appspot.com/bug?extid=caa0c2c363b91f7b6fdf
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [johan....@gmail.com linux-b...@vger.kernel.org linux-...@vger.kernel.org luiz....@gmail.com mar...@holtmann.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/beb425a1a5b6/disk-5d2f5353.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5cf20e23a924/vmlinux-5d2f5353.xz
kernel image: https://storage.googleapis.com/syzbot-assets/13f3775e9dd1/bzImage-5d2f5353.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff888021d2e348 object type: work_struct hint: hci_conn_timeout+0x0/0x280
WARNING: CPU: 0 PID: 5073 at lib/debugobjects.c:517 debug_print_object+0x173/0x1e0 lib/debugobjects.c:514
Modules linked in:
CPU: 0 PID: 5073 Comm: kworker/u5:3 Not tainted 6.6.0-rc2-syzkaller-00027-g5d2f53532ecc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
Workqueue: hci5 hci_cmd_sync_work
RIP: 0010:debug_print_object+0x173/0x1e0 lib/debugobjects.c:514
Code: df e8 71 9d a2 fd 4c 8b 0b 48 c7 c7 00 a0 59 8b 48 8b 74 24 08 48 89 ea 44 89 e1 4d 89 f8 ff 34 24 e8 91 5a 0e fd 48 83 c4 08 <0f> 0b ff 05 75 c6 54 0a 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d
RSP: 0018:ffffc90003eef888 EFLAGS: 00010286
RAX: 8c31f90cc3226700 RBX: ffffffff8b09d4a0 RCX: ffff8880255abb80
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffffff8b59a180 R08: ffffffff81543312 R09: 1ffff920007dde64
R10: dffffc0000000000 R11: fffff520007dde65 R12: 0000000000000000
R13: ffffffff8b59a098 R14: dffffc0000000000 R15: ffff888021d2e348
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffce85c1ff8 CR3: 00000000837df000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:1032 [inline]
debug_check_no_obj_freed+0x2f7/0x420 lib/debugobjects.c:1063
slab_free_hook mm/slub.c:1775 [inline]
slab_free_freelist_hook mm/slub.c:1826 [inline]
slab_free mm/slub.c:3809 [inline]
__kmem_cache_free+0x20c/0x3b0 mm/slub.c:3822
device_release+0x95/0x1c0
kobject_cleanup lib/kobject.c:682 [inline]
kobject_release lib/kobject.c:716 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x1ee/0x430 lib/kobject.c:733
hci_abort_conn_sync+0xa2d/0xf40
hci_cmd_sync_work+0x238/0x390 net/bluetooth/hci_sync.c:306
process_one_work kernel/workqueue.c:2630 [inline]
process_scheduled_works+0x90f/0x1400 kernel/workqueue.c:2703
worker_thread+0xa5f/0xff0 kernel/workqueue.c:2784
kthread+0x2d3/0x370 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

If the bug is a duplicate of another bug, 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.