[v6.1] WARNING: ODEBUG bug in usb_unbind_interface (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d7039b844a1c Linux 6.1.116
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=168acb5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a047880f6dd12cce
dashboard link: https://syzkaller.appspot.com/bug?extid=ce1634759da7a7b81356
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/b531abf1deab/disk-d7039b84.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6780cfcf0543/vmlinux-d7039b84.xz
kernel image: https://storage.googleapis.com/syzbot-assets/398543175ad2/bzImage-d7039b84.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: work_struct hint: usbnet_deferred_kevent+0x0/0xc10
WARNING: CPU: 0 PID: 4332 at lib/debugobjects.c:518 debug_print_object lib/debugobjects.c:515 [inline]
WARNING: CPU: 0 PID: 4332 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:979 [inline]
WARNING: CPU: 0 PID: 4332 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x38e/0x4e0 lib/debugobjects.c:1009
Modules linked in:
CPU: 0 PID: 4332 Comm: kworker/0:8 Not tainted 6.1.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: usb_hub_wq hub_event
RIP: 0010:debug_print_object lib/debugobjects.c:515 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:979 [inline]
RIP: 0010:debug_check_no_obj_freed+0x38e/0x4e0 lib/debugobjects.c:1009
Code: ef e8 36 4e a3 fd 4c 8b 45 00 48 c7 c7 20 81 5d 8b 48 c7 c6 e0 7d 5d 8b 48 c7 c2 80 82 5d 8b 8b 0c 24 49 89 d9 e8 72 df 13 fd <0f> 0b ff 05 72 76 5b 0a 48 83 c5 30 48 89 e8 48 c1 e8 03 48 b9 00
RSP: 0018:ffffc9000470f418 EFLAGS: 00010246
RAX: 5b1f4e2000697e00 RBX: ffffffff86553580 RCX: 0000000000100000
RDX: ffffc9001751d000 RSI: 0000000000045993 RDI: 0000000000045994
RBP: ffffffff8b0b3640 R08: ffffffff8152a88e R09: fffff520008e1de5
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888060869160
R13: ffffffff9757ab98 R14: ffff88806086a000 R15: ffff88805d1e2288
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe7fd99358 CR3: 000000000d08e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 000000000000000a DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1699 [inline]
slab_free_freelist_hook mm/slub.c:1750 [inline]
slab_free mm/slub.c:3661 [inline]
__kmem_cache_free+0x205/0x3c0 mm/slub.c:3674
device_release+0x91/0x1c0
kobject_cleanup lib/kobject.c:681 [inline]
kobject_release lib/kobject.c:712 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x224/0x460 lib/kobject.c:729
usb_unbind_interface+0x1cd/0x840 drivers/usb/core/driver.c:458
device_remove drivers/base/dd.c:550 [inline]
__device_release_driver drivers/base/dd.c:1260 [inline]
device_release_driver_internal+0x59e/0x880 drivers/base/dd.c:1286
bus_remove_device+0x2e5/0x400 drivers/base/bus.c:531
device_del+0x6e2/0xbd0 drivers/base/core.c:3877
usb_disable_device+0x3b8/0x840 drivers/usb/core/message.c:1414
usb_disconnect+0x33c/0x8c0 drivers/usb/core/hub.c:2275
hub_port_connect drivers/usb/core/hub.c:5321 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5617 [inline]
port_event drivers/usb/core/hub.c:5773 [inline]
hub_event+0x1f78/0x5730 drivers/usb/core/hub.c:5855
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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