[moderation] [usb?] general protection fault in usb_gadget_udc_reset (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 08b06c30a445 Merge tag 'v6.17-rc4-ksmbd-fix' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1427e962580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd9738e00c1bbfb4
dashboard link: https://syzkaller.appspot.com/bug?extid=d0a16f171e7671365695
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org linu...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/310df2cd9e4b/disk-08b06c30.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/180086192d29/vmlinux-08b06c30.xz
kernel image: https://storage.googleapis.com/syzbot-assets/503e30dde381/bzImage-08b06c30.xz

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

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000008: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]
CPU: 0 UID: 0 PID: 6018 Comm: kworker/0:6 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: events __usb_queue_reset_device
RIP: 0010:usb_gadget_udc_reset+0x29/0xb0 drivers/usb/gadget/udc/core.c:1191
Code: 90 f3 0f 1e fa 41 57 41 56 53 49 89 f6 48 89 fb 49 bf 00 00 00 00 00 fc ff df e8 02 f0 c2 fa 49 83 c6 40 4c 89 f0 48 c1 e8 03 <42> 80 3c 38 00 74 08 4c 89 f7 e8 f8 29 22 fb 4d 8b 1e 48 89 df 41
RSP: 0018:ffffc900056b7338 EFLAGS: 00010202
RAX: 0000000000000008 RBX: ffff888145b90c40 RCX: ffff88802e2d0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff88803a390164 R08: ffffffff8f1d5137 R09: 1ffffffff1e3aa26
R10: dffffc0000000000 R11: fffffbfff1e3aa27 R12: ffff888145b90c40
R13: 1ffff11028be6ea1 R14: 0000000000000040 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881268c1000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555593a6b608 CR3: 000000003b08e000 CR4: 00000000003526f0
Call Trace:
<TASK>
set_link_state+0x80b/0x1220 drivers/usb/gadget/udc/dummy_hcd.c:469
dummy_hub_control+0xcc0/0x1760 drivers/usb/gadget/udc/dummy_hcd.c:2327
rh_call_control drivers/usb/core/hcd.c:656 [inline]
rh_urb_enqueue drivers/usb/core/hcd.c:821 [inline]
usb_hcd_submit_urb+0xde9/0x1a80 drivers/usb/core/hcd.c:1542
usb_start_wait_urb+0x114/0x4c0 drivers/usb/core/message.c:59
usb_internal_control_msg drivers/usb/core/message.c:103 [inline]
usb_control_msg+0x232/0x3e0 drivers/usb/core/message.c:154
set_port_feature drivers/usb/core/hub.c:470 [inline]
hub_port_reset+0x390/0x1740 drivers/usb/core/hub.c:3082
hub_port_init+0x2b0/0x2800 drivers/usb/core/hub.c:4938
usb_reset_and_verify_device+0x4cd/0x1a80 drivers/usb/core/hub.c:6214
usb_reset_device+0x552/0xae0 drivers/usb/core/hub.c:6409
__usb_queue_reset_device+0x73/0xa0 drivers/usb/core/message.c:1904
process_one_work kernel/workqueue.c:3236 [inline]
process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
kthread+0x70e/0x8a0 kernel/kthread.c:463
ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:usb_gadget_udc_reset+0x29/0xb0 drivers/usb/gadget/udc/core.c:1191
Code: 90 f3 0f 1e fa 41 57 41 56 53 49 89 f6 48 89 fb 49 bf 00 00 00 00 00 fc ff df e8 02 f0 c2 fa 49 83 c6 40 4c 89 f0 48 c1 e8 03 <42> 80 3c 38 00 74 08 4c 89 f7 e8 f8 29 22 fb 4d 8b 1e 48 89 df 41
RSP: 0018:ffffc900056b7338 EFLAGS: 00010202
RAX: 0000000000000008 RBX: ffff888145b90c40 RCX: ffff88802e2d0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff88803a390164 R08: ffffffff8f1d5137 R09: 1ffffffff1e3aa26
R10: dffffc0000000000 R11: fffffbfff1e3aa27 R12: ffff888145b90c40
R13: 1ffff11028be6ea1 R14: 0000000000000040 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881268c1000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555593a6b608 CR3: 000000003b08e000 CR4: 00000000003526f0
----------------
Code disassembly (best guess):
0: 90 nop
1: f3 0f 1e fa endbr64
5: 41 57 push %r15
7: 41 56 push %r14
9: 53 push %rbx
a: 49 89 f6 mov %rsi,%r14
d: 48 89 fb mov %rdi,%rbx
10: 49 bf 00 00 00 00 00 movabs $0xdffffc0000000000,%r15
17: fc ff df
1a: e8 02 f0 c2 fa call 0xfac2f021
1f: 49 83 c6 40 add $0x40,%r14
23: 4c 89 f0 mov %r14,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 f7 mov %r14,%rdi
34: e8 f8 29 22 fb call 0xfb222a31
39: 4d 8b 1e mov (%r14),%r11
3c: 48 89 df mov %rbx,%rdi
3f: 41 rex.B


---
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