[syzbot] [usb?] WARNING: ODEBUG bug in usb_unbind_interface (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b6ea1680d0ac Merge tag 'v6.15-p6' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1131b1b3980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a9a25b7a36123454
dashboard link: https://syzkaller.appspot.com/bug?extid=52ba12be8e4d18263247
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d847e7b2a66a/disk-b6ea1680.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c4dcc4871fb2/vmlinux-b6ea1680.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7b8bf844d89e/bzImage-b6ea1680.xz

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

WARNING: CPU: 0 PID: 6729 at lib/debugobjects.c:615 debug_print_object+0x16b/0x1e0 lib/debugobjects.c:612
Modules linked in:
CPU: 0 UID: 0 PID: 6729 Comm: kworker/0:11 Not tainted 6.15.0-rc4-syzkaller-00042-gb6ea1680d0ac #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Workqueue: usb_hub_wq hub_event
RIP: 0010:debug_print_object+0x16b/0x1e0 lib/debugobjects.c:612
Code: 4c 89 ff e8 b7 6b 63 fd 4d 8b 0f 48 c7 c7 80 d7 c1 8b 48 8b 34 24 4c 89 ea 89 e9 4d 89 f0 41 54 e8 6a d4 c5 fc 48 83 c4 08 90 <0f> 0b 90 90 ff 05 17 ba c0 0a 48 83 c4 08 5b 41 5c 41 5d 41 5e 41
RSP: 0018:ffffc900037df320 EFLAGS: 00010292
RAX: ca5e4d58fd900000 RBX: dffffc0000000000 RCX: 0000000000100000
RDX: ffffc90014e77000 RSI: 000000000002265c RDI: 000000000002265d
RBP: 0000000000000000 R08: ffffffff8f7ed377 R09: 1ffffffff1efda6e
R10: dffffc0000000000 R11: fffffbfff1efda6f R12: ffffffff86fb2200
R13: ffffffff8bc1d900 R14: ffff88804f0b1260 R15: ffffffff8b69bc40
FS: 0000000000000000(0000) GS:ffff8881260cc000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000404000 CR3: 000000006e344000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 000000000000000e DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:1099 [inline]
debug_check_no_obj_freed+0x3a2/0x470 lib/debugobjects.c:1129
slab_free_hook mm/slub.c:2329 [inline]
slab_free mm/slub.c:4656 [inline]
kfree+0x117/0x440 mm/slub.c:4855
device_release+0x99/0x1c0 drivers/base/core.c:-1
kobject_cleanup lib/kobject.c:689 [inline]
kobject_release lib/kobject.c:720 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x228/0x480 lib/kobject.c:737
usb_unbind_interface+0x26b/0x8f0 drivers/usb/core/driver.c:458
device_remove drivers/base/dd.c:569 [inline]
__device_release_driver drivers/base/dd.c:1272 [inline]
device_release_driver_internal+0x4d6/0x7c0 drivers/base/dd.c:1295
bus_remove_device+0x34d/0x410 drivers/base/bus.c:579
device_del+0x511/0x8e0 drivers/base/core.c:3881
usb_disable_device+0x3e9/0x8a0 drivers/usb/core/message.c:1418
usb_disconnect+0x330/0x910 drivers/usb/core/hub.c:2316
hub_port_connect drivers/usb/core/hub.c:5371 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5671 [inline]
port_event drivers/usb/core/hub.c:5831 [inline]
hub_event+0x1cdb/0x4a00 drivers/usb/core/hub.c:5913
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xadb/0x17a0 kernel/workqueue.c:3319
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
kthread+0x70e/0x8a0 kernel/kthread.c:464
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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.