[v5.15] WARNING: ODEBUG bug in usb_unbind_interface

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6f7927ac664 Linux 5.15.127
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11ae7523a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea39ec6ccd2c5d32
dashboard link: https://syzkaller.appspot.com/bug?extid=1b16731380e7c0300371
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=137a673da80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e290f46611c7/disk-f6f7927a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/64ee0ddb7c8c/vmlinux-f6f7927a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c32675f93c1/bzImage-f6f7927a.xz

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

usb 5-1: USB disconnect, device number 10
cdc_ncm 5-1:1.0 usb3: unregister 'cdc_ncm' usb-dummy_hcd.4-1, CDC NCM
------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: work_struct hint: usbnet_deferred_kevent+0x0/0xb20 drivers/net/usb/usbnet.c:1585
WARNING: CPU: 0 PID: 7 at lib/debugobjects.c:511 debug_print_object lib/debugobjects.c:508 [inline]
WARNING: CPU: 0 PID: 7 at lib/debugobjects.c:511 __debug_check_no_obj_freed lib/debugobjects.c:1006 [inline]
WARNING: CPU: 0 PID: 7 at lib/debugobjects.c:511 debug_check_no_obj_freed+0x451/0x610 lib/debugobjects.c:1037
Modules linked in:

CPU: 0 PID: 7 Comm: kworker/0:0 Not tainted 5.15.127-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: usb_hub_wq hub_event
RIP: 0010:debug_print_object lib/debugobjects.c:508 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:1006 [inline]
RIP: 0010:debug_check_no_obj_freed+0x451/0x610 lib/debugobjects.c:1037
Code: 74 08 48 89 ef e8 8f 2f be fd 48 8b 13 4c 8b 45 00 48 c7 c7 c0 81 d8 8a 48 c7 c6 e0 7e d8 8a 44 89 f1 4d 89 f9 e8 5f 58 40 fd <0f> 0b 48 ba 00 00 00 00 00 fc ff df 4c 8b 74 24 38 ff 05 b0 b6 d8
RSP: 0018:ffffc90000cc7388 EFLAGS: 00010246
RAX: ca2ad4b75f431f00 RBX: ffffffff8ad88238 RCX: ffff8880129b3b80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffffff8a8a3c60 R08: ffffffff816658fc R09: ffffed10173467a8
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffffff8a8a3c60
R13: ffff888075a96608 R14: 0000000000000000 R15: ffffffff86028b60
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ba50a24131 CR3: 000000007aedf000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1680 [inline]
slab_free_freelist_hook+0x86/0x160 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kfree+0xf1/0x270 mm/slub.c:4559
device_release+0x91/0x1c0
kobject_cleanup lib/kobject.c:713 [inline]
kobject_release lib/kobject.c:744 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x224/0x460 lib/kobject.c:761
usb_unbind_interface+0x1cd/0x840 drivers/usb/core/driver.c:458
__device_release_driver drivers/base/dd.c:1229 [inline]
device_release_driver_internal+0x50e/0x7f0 drivers/base/dd.c:1262
bus_remove_device+0x2e5/0x400 drivers/base/bus.c:529
device_del+0x6e2/0xbd0 drivers/base/core.c:3582
usb_disable_device+0x3b8/0x840 drivers/usb/core/message.c:1419
usb_disconnect+0x33c/0x8c0 drivers/usb/core/hub.c:2231
hub_port_connect drivers/usb/core/hub.c:5202 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5502 [inline]
port_event drivers/usb/core/hub.c:5648 [inline]
hub_event+0x1e63/0x56d0 drivers/usb/core/hub.c:5730
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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 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 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