[v6.6] WARNING: ODEBUG bug in smsusb_term_device

2 views
Skip to first unread message

syzbot

unread,
Jul 1, 2025, 8:16:34 PM7/1/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f5b4c104b7d Linux 6.6.95
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11a3f88c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b80883c3ded77c16
dashboard link: https://syzkaller.appspot.com/bug?extid=43d74f10ce31406ed938
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0efd4e01816e/disk-3f5b4c10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f7c9d20858cc/vmlinux-3f5b4c10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/18f8dc74ef68/bzImage-3f5b4c10.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff888079666688 object type: work_struct hint: do_submit_urb+0x0/0x360 drivers/media/usb/siano/smsusb.c:-1
WARNING: CPU: 1 PID: 7523 at lib/debugobjects.c:518 debug_print_object lib/debugobjects.c:515 [inline]
WARNING: CPU: 1 PID: 7523 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
WARNING: CPU: 1 PID: 7523 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Modules linked in:
CPU: 1 PID: 7523 Comm: kworker/1:6 Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
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:990 [inline]
RIP: 0010:debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Code: 4c 8b 4d 00 48 c7 c7 80 74 fc 8a 48 c7 c6 e0 70 fc 8a 48 c7 c2 00 76 fc 8a 8b 0c 24 4d 89 f8 41 55 e8 8e 77 29 fd 48 83 c4 08 <0f> 0b 4c 8b 6c 24 18 48 b9 00 00 00 00 00 fc ff df ff 05 a3 5d 23
RSP: 0018:ffffc9000bde6b38 EFLAGS: 00010282
RAX: 4790274bd8f75e00 RBX: ffffffff971200c8 RCX: 0000000000100000
RDX: ffffc90017cac000 RSI: 0000000000065cb5 RDI: 0000000000065cb6
RBP: ffffffff8aa9dfe0 R08: ffffc9000bde6727 R09: 1ffff920017bcce4
R10: dffffc0000000000 R11: fffff520017bcce5 R12: ffff888079667000
R13: ffffffff870bd5e0 R14: ffff888079666000 R15: ffff888079666688
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3a41ae CR3: 000000007dbd6000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1781 [inline]
slab_free_freelist_hook+0xd2/0x1b0 mm/slub.c:1832
slab_free mm/slub.c:3816 [inline]
__kmem_cache_free+0xba/0x1f0 mm/slub.c:3829
smsusb_term_device+0x1ac/0x220 drivers/media/usb/siano/smsusb.c:352
smsusb_init_device drivers/media/usb/siano/smsusb.c:491 [inline]
smsusb_probe+0x1708/0x1da0 drivers/media/usb/siano/smsusb.c:569
usb_probe_interface+0x5a4/0xb00 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x25b/0xb40 drivers/base/dd.c:658
__driver_probe_device+0x18c/0x330 drivers/base/dd.c:800
driver_probe_device+0x4f/0x420 drivers/base/dd.c:830
__device_attach_driver+0x2ca/0x520 drivers/base/dd.c:958
bus_for_each_drv+0x24b/0x2d0 drivers/base/bus.c:459
__device_attach+0x2b5/0x400 drivers/base/dd.c:1030
bus_probe_device+0x180/0x260 drivers/base/bus.c:534
device_add+0x85b/0xc20 drivers/base/core.c:3683
usb_set_configuration+0x1a79/0x20c0 drivers/usb/core/message.c:2207
usb_generic_driver_probe+0x8d/0x150 drivers/usb/core/generic.c:238
usb_probe_device+0x13d/0x280 drivers/usb/core/driver.c:293
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x25b/0xb40 drivers/base/dd.c:658
__driver_probe_device+0x18c/0x330 drivers/base/dd.c:800
driver_probe_device+0x4f/0x420 drivers/base/dd.c:830
__device_attach_driver+0x2ca/0x520 drivers/base/dd.c:958
bus_for_each_drv+0x24b/0x2d0 drivers/base/bus.c:459
__device_attach+0x2b5/0x400 drivers/base/dd.c:1030
bus_probe_device+0x180/0x260 drivers/base/bus.c:534
device_add+0x85b/0xc20 drivers/base/core.c:3683
usb_new_device+0xa31/0x1630 drivers/usb/core/hub.c:2632
hub_port_connect drivers/usb/core/hub.c:5501 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5641 [inline]
port_event drivers/usb/core/hub.c:5801 [inline]
hub_event+0x2957/0x49c0 drivers/usb/core/hub.c:5883
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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

unread,
Jul 2, 2025, 12:26:35 PM7/2/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 3f5b4c104b7d Linux 6.6.95
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11803770580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b80883c3ded77c16
dashboard link: https://syzkaller.appspot.com/bug?extid=43d74f10ce31406ed938
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c4d3d4580000
mounted in repro: https://storage.googleapis.com/syzbot-assets/19f1605eb004/mount_0.gz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff888077aa2688 object type: work_struct hint: do_submit_urb+0x0/0x360 drivers/media/usb/siano/smsusb.c:-1
WARNING: CPU: 1 PID: 28 at lib/debugobjects.c:518 debug_print_object lib/debugobjects.c:515 [inline]
WARNING: CPU: 1 PID: 28 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
WARNING: CPU: 1 PID: 28 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Modules linked in:
CPU: 1 PID: 28 Comm: kworker/1:1 Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
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:990 [inline]
RIP: 0010:debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Code: 4c 8b 4d 00 48 c7 c7 80 74 fc 8a 48 c7 c6 e0 70 fc 8a 48 c7 c2 00 76 fc 8a 8b 0c 24 4d 89 f8 41 55 e8 8e 77 29 fd 48 83 c4 08 <0f> 0b 4c 8b 6c 24 18 48 b9 00 00 00 00 00 fc ff df ff 05 a3 5d 23
RSP: 0018:ffffc90000a4eb38 EFLAGS: 00010282
RAX: 07c1457f560fd700 RBX: ffffffff9711be68 RCX: ffff88801ce69e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffffff8aa9dfe0 R08: ffffc90000a4e727 R09: 1ffff92000149ce4
R10: dffffc0000000000 R11: fffff52000149ce5 R12: ffff888077aa3000
R13: ffffffff870bd5e0 R14: ffff888077aa2000 R15: ffff888077aa2688
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f765dda8fe0 CR3: 000000000cb30000 CR4: 00000000003506e0
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.

syzbot

unread,
Jul 2, 2025, 5:04:29 PM7/2/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 3f5b4c104b7d Linux 6.6.95
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12d6d3d4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b80883c3ded77c16
dashboard link: https://syzkaller.appspot.com/bug?extid=43d74f10ce31406ed938
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1062b48c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d6d3d4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0efd4e01816e/disk-3f5b4c10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f7c9d20858cc/vmlinux-3f5b4c10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/18f8dc74ef68/bzImage-3f5b4c10.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff8880192f67a8 object type: work_struct hint: do_submit_urb+0x0/0x360 drivers/media/usb/siano/smsusb.c:-1
WARNING: CPU: 0 PID: 9 at lib/debugobjects.c:518 debug_print_object lib/debugobjects.c:515 [inline]
WARNING: CPU: 0 PID: 9 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
WARNING: CPU: 0 PID: 9 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Modules linked in:
CPU: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
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:990 [inline]
RIP: 0010:debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Code: 4c 8b 4d 00 48 c7 c7 80 74 fc 8a 48 c7 c6 e0 70 fc 8a 48 c7 c2 00 76 fc 8a 8b 0c 24 4d 89 f8 41 55 e8 8e 77 29 fd 48 83 c4 08 <0f> 0b 4c 8b 6c 24 18 48 b9 00 00 00 00 00 fc ff df ff 05 a3 5d 23
RSP: 0018:ffffc900000e6b38 EFLAGS: 00010282
RAX: 1ae6a89fa06d3900 RBX: ffffffff970d03a0 RCX: ffff888019e78000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffffff8aa9dfe0 R08: ffffc900000e6827 R09: 1ffff9200001cd04
R10: dffffc0000000000 R11: fffff5200001cd05 R12: ffff8880192f7000
R13: ffffffff870bd5e0 R14: ffff8880192f6000 R15: ffff8880192f67a8
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555575224808 CR3: 000000007ddcf000 CR4: 00000000003506f0
Reply all
Reply to author
Forward
0 new messages