[moderation] [kernel?] WARNING: ODEBUG bug in free_netdev (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 186f3edfdd41 Merge tag 'pinctrl-v6.17-1' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1111f834580000
kernel config: https://syzkaller.appspot.com/x/.config?x=25f3811092551870
dashboard link: https://syzkaller.appspot.com/bug?extid=8bfd7bcc98f7300afb84
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [da...@kernel.org gre...@linuxfoundation.org linux-...@vger.kernel.org raf...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ac348bc49788/disk-186f3edf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/037580577afc/vmlinux-186f3edf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cd2b853d4729/bzImage-186f3edf.xz

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

WARNING: CPU: 1 PID: 5912 at lib/debugobjects.c:612 debug_print_object+0x1a2/0x2b0 lib/debugobjects.c:612
Modules linked in:
CPU: 1 UID: 0 PID: 5912 Comm: kworker/1:4 Not tainted 6.16.0-syzkaller-11241-g186f3edfdd41 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: usb_hub_wq hub_event
RIP: 0010:debug_print_object+0x1a2/0x2b0 lib/debugobjects.c:612
Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 54 41 56 48 8b 14 dd 60 0c 16 8c 4c 89 e6 48 c7 c7 e0 00 16 8c e8 7f 64 90 fc 90 <0f> 0b 90 90 58 83 05 16 3b c1 0b 01 48 83 c4 18 5b 5d 41 5c 41 5d
RSP: 0000:ffffc9000409f408 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffc9001adc4000
RDX: 0000000000100000 RSI: ffffffff817a3075 RDI: 0000000000000001
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: fffffffffffe7e28 R12: ffffffff8c160780
R13: ffffffff8bac16a0 R14: ffffffff87261060 R15: ffffc9000409f508
FS: 0000000000000000(0000) GS:ffff8881247c8000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f35d4f37090 CR3: 00000000315c0000 CR4: 00000000003526f0
DR0: 000000000000004b DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:1099 [inline]
debug_check_no_obj_freed+0x4b7/0x600 lib/debugobjects.c:1129
slab_free_hook mm/slub.c:2348 [inline]
slab_free mm/slub.c:4680 [inline]
kfree+0x28f/0x4d0 mm/slub.c:4879
device_release+0xa4/0x240 drivers/base/core.c:2565
kobject_cleanup lib/kobject.c:689 [inline]
kobject_release lib/kobject.c:720 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x1e7/0x5a0 lib/kobject.c:737
put_device+0x1f/0x30 drivers/base/core.c:3797
free_netdev+0x619/0x910 net/core/dev.c:11992
usbnet_disconnect+0x25c/0x500 drivers/net/usb/usbnet.c:1673
usb_unbind_interface+0x1da/0x9e0 drivers/usb/core/driver.c:458
device_remove drivers/base/dd.c:571 [inline]
device_remove+0x122/0x170 drivers/base/dd.c:563
__device_release_driver drivers/base/dd.c:1274 [inline]
device_release_driver_internal+0x44b/0x620 drivers/base/dd.c:1297
bus_remove_device+0x22f/0x420 drivers/base/bus.c:579
device_del+0x396/0x9f0 drivers/base/core.c:3878
usb_disable_device+0x355/0x7d0 drivers/usb/core/message.c:1418
usb_disconnect+0x2e1/0x9c0 drivers/usb/core/hub.c:2344
hub_port_connect drivers/usb/core/hub.c:5406 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5706 [inline]
port_event drivers/usb/core/hub.c:5870 [inline]
hub_event+0x1c81/0x4fe0 drivers/usb/core/hub.c:5952
process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3236
process_scheduled_works kernel/workqueue.c:3319 [inline]
worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400
kthread+0x3c5/0x780 kernel/kthread.c:464
ret_from_fork+0x5d7/0x6f0 arch/x86/kernel/process.c:148
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.