[v6.1] WARNING: ODEBUG bug in smsusb_term_device

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 03f3a99e8e93 Linux 6.1.181
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=153c3e49580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=7a0635ebb59ba4cb8a82
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5b5f6916be1c/disk-03f3a99e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/40dfca357207/vmlinux-03f3a99e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2c9ae944921f/bzImage-03f3a99e.xz

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

smsmdtv:smscore_unregister_device: exiting although not all buffers released.
------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: work_struct hint: do_submit_urb+0x0/0x3c0
WARNING: CPU: 0 PID: 4360 at lib/debugobjects.c:518 debug_print_object lib/debugobjects.c:515 [inline]
WARNING: CPU: 0 PID: 4360 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:1045 [inline]
WARNING: CPU: 0 PID: 4360 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x395/0x520 lib/debugobjects.c:1075
Modules linked in:
CPU: 0 PID: 4360 Comm: kworker/0:8 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
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:1045 [inline]
RIP: 0010:debug_check_no_obj_freed+0x395/0x520 lib/debugobjects.c:1075
Code: e8 d0 1a b9 fd 4c 8b 45 00 48 c7 c7 a0 67 df 8a 48 c7 c6 00 64 df 8a 48 c7 c2 00 69 df 8a 8b 4c 24 1c 4d 89 e9 e8 3b 78 33 fd <0f> 0b 4c 8b 6c 24 10 48 b9 00 00 00 00 00 fc ff df ff 05 7c ff 06
RSP: 0000:ffffc90004716c68 EFLAGS: 00010246
RAX: 3d08ff9e461dcd00 RBX: ffffffff96e3fc60 RCX: 0000000000100000
RDX: ffffc9001b40c000 RSI: 00000000000354f6 RDI: 00000000000354f7
RBP: ffffffff8a8b4a60 R08: ffffc900047168e7 R09: 1ffff920008e2d1c
R10: dffffc0000000000 R11: fffff520008e2d1d R12: 0000000000000001
R13: ffffffff86e75160 R14: ffff8880262e8000 R15: ffff8880262e8328
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3a491d3000 CR3: 000000001e7c7000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1704 [inline]
slab_free_freelist_hook+0xd2/0x1b0 mm/slub.c:1755
slab_free mm/slub.c:3687 [inline]
__kmem_cache_free+0xb6/0x200 mm/slub.c:3700
smsusb_term_device+0x1a5/0x220 drivers/media/usb/siano/smsusb.c:352
smsusb_init_device drivers/media/usb/siano/smsusb.c:491 [inline]
smsusb_probe+0x172a/0x1dd0 drivers/media/usb/siano/smsusb.c:569
usb_probe_interface+0x5be/0xae0 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x24a/0xb40 drivers/base/dd.c:638
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:804
driver_probe_device+0x4f/0x420 drivers/base/dd.c:834
__device_attach_driver+0x2c6/0x510 drivers/base/dd.c:962
bus_for_each_drv+0x184/0x210 drivers/base/bus.c:429
__device_attach+0x2a7/0x480 drivers/base/dd.c:1034
bus_probe_device+0xba/0x1d0 drivers/base/bus.c:489
device_add+0xbcf/0x1050 drivers/base/core.c:3712
usb_set_configuration+0x19d5/0x2030 drivers/usb/core/message.c:2223
usb_generic_driver_probe+0x89/0x150 drivers/usb/core/generic.c:238
usb_probe_device+0x126/0x250 drivers/usb/core/driver.c:293
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x24a/0xb40 drivers/base/dd.c:638
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:804
driver_probe_device+0x4f/0x420 drivers/base/dd.c:834
__device_attach_driver+0x2c6/0x510 drivers/base/dd.c:962
bus_for_each_drv+0x184/0x210 drivers/base/bus.c:429
__device_attach+0x2a7/0x480 drivers/base/dd.c:1034
bus_probe_device+0xba/0x1d0 drivers/base/bus.c:489
device_add+0xbcf/0x1050 drivers/base/core.c:3712
usb_new_device+0xa01/0x15e0 drivers/usb/core/hub.c:2659
hub_port_connect drivers/usb/core/hub.c:5517 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
port_event drivers/usb/core/hub.c:5817 [inline]
hub_event+0x2b2f/0x5200 drivers/usb/core/hub.c:5899
process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
worker_thread+0xaf5/0x12a0 kernel/workqueue.c:2439
kthread+0x29d/0x330 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