[v6.1] WARNING: ODEBUG bug in usb_unbind_interface

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 61fd484b2cf6 Linux 6.1.38
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=179d49e4a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=43a813745c91c8b3
dashboard link: https://syzkaller.appspot.com/bug?extid=8efbdabe5f8fc269aa38
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/f3fe059efa91/disk-61fd484b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b69bfadef125/vmlinux-61fd484b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ecbf54ec382/bzImage-61fd484b.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: work_struct hint: usbnet_deferred_kevent+0x0/0xb80 drivers/net/usb/usbnet.c:1584
WARNING: CPU: 0 PID: 936 at lib/debugobjects.c:508 debug_print_object lib/debugobjects.c:505 [inline]
WARNING: CPU: 0 PID: 936 at lib/debugobjects.c:508 __debug_check_no_obj_freed lib/debugobjects.c:1012 [inline]
WARNING: CPU: 0 PID: 936 at lib/debugobjects.c:508 debug_check_no_obj_freed+0x451/0x610 lib/debugobjects.c:1043
Modules linked in:
CPU: 0 PID: 936 Comm: kworker/0:2 Not tainted 6.1.38-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
Workqueue: usb_hub_wq hub_event
RIP: 0010:debug_print_object lib/debugobjects.c:505 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:1012 [inline]
RIP: 0010:debug_check_no_obj_freed+0x451/0x610 lib/debugobjects.c:1043
Code: 74 08 48 89 ef e8 5f e6 a6 fd 48 8b 13 4c 8b 45 00 48 c7 c7 60 d7 3c 8b 48 c7 c6 80 d4 3c 8b 44 89 f1 4d 89 f9 e8 5f ef 18 fd <0f> 0b 48 ba 00 00 00 00 00 fc ff df 4c 8b 74 24 38 ff 05 b0 2d 1a
RSP: 0018:ffffc9000464f3d8 EFLAGS: 00010246
RAX: 9644097f5c0d0000 RBX: ffffffff8b3cd7d8 RCX: 0000000000040000
RDX: ffffc90014751000 RSI: 000000000001967f RDI: 0000000000019680
RBP: ffffffff8aeb0820 R08: ffffffff81524cae R09: fffff520008c9df5
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffffff8aeb0820
R13: ffff8880790d0058 R14: 0000000000000000 R15: ffffffff864a3c40
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc3b00f4000 CR3: 00000000381b2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 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:1258 [inline]
device_release_driver_internal+0x59e/0x880 drivers/base/dd.c:1284
bus_remove_device+0x2e5/0x400 drivers/base/bus.c:529
device_del+0x6e2/0xbd0 drivers/base/core.c:3852
usb_disable_device+0x3b8/0x840 drivers/usb/core/message.c:1419
usb_disconnect+0x33c/0x8c0 drivers/usb/core/hub.c:2238
hub_port_connect drivers/usb/core/hub.c:5199 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5499 [inline]
port_event drivers/usb/core/hub.c:5655 [inline]
hub_event+0x1dfa/0x57b0 drivers/usb/core/hub.c:5737
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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 change 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.