[moderation] [usb?] general protection fault in dummy_wakeup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0ce37745d4bf Merge tag 'block-7.2-20260724' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11072449580000
kernel config: https://syzkaller.appspot.com/x/.config?x=145fa60d73086782
dashboard link: https://syzkaller.appspot.com/bug?extid=bad390114398d3e151b7
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
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/19521188f055/disk-0ce37745.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2f7922f1fe08/vmlinux-0ce37745.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1a7a0ce66cfa/bzImage-0ce37745.xz

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

ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 1 UID: 0 PID: 1311 Comm: aoe_tx0 Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:dummy_wakeup+0x95/0x300 drivers/usb/gadget/udc/dummy_hcd.c:865
Code: c1 ea 03 80 3c 02 00 0f 85 65 02 00 00 48 8b 9b 90 06 00 00 e8 7c a9 39 fa 48 89 da 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 31 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b
RSP: 0018:ffffc90005a4f8b8 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff87d0b2e8
RDX: 0000000000000000 RSI: ffffffff87d0b324 RDI: ffff888025fd1290
RBP: 0000000000000003 R08: 0000000000000005 R09: 0000000000000005
R10: 0000000000000003 R11: 0000000000000000 R12: ffff8880293ca000
R13: 000000010000ac01 R14: ffff88804ebc4ec0 R15: ffff88804ebc4f00
FS: 0000000000000000(0000) GS:ffff888123ede000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f238680cff8 CR3: 000000005dc94000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 000000000000000b
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_gadget_wakeup+0x6e/0x2a0 drivers/usb/gadget/udc/core.c:524
ether_wakeup_host drivers/usb/gadget/function/u_ether.c:452 [inline]
eth_start_xmit+0xef6/0x1390 drivers/usb/gadget/function/u_ether.c:481
__netdev_start_xmit include/linux/netdevice.h:5400 [inline]
netdev_start_xmit include/linux/netdevice.h:5409 [inline]
xmit_one net/core/dev.c:3889 [inline]
dev_hard_start_xmit+0x121/0x760 net/core/dev.c:3905
sch_direct_xmit+0x1b2/0xc70 net/sched/sch_generic.c:372
__dev_xmit_skb net/core/dev.c:4214 [inline]
__dev_queue_xmit+0x27ac/0x4970 net/core/dev.c:4836
dev_queue_xmit include/linux/netdevice.h:3446 [inline]
tx+0xc4/0x130 drivers/block/aoe/aoenet.c:62
kthread+0x1d8/0x3c0 drivers/block/aoe/aoecmd.c:1241
kthread+0x370/0x450 kernel/kthread.c:436
ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:dummy_wakeup+0x95/0x300 drivers/usb/gadget/udc/dummy_hcd.c:865
Code: c1 ea 03 80 3c 02 00 0f 85 65 02 00 00 48 8b 9b 90 06 00 00 e8 7c a9 39 fa 48 89 da 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 31 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b
RSP: 0018:ffffc90005a4f8b8 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff87d0b2e8
RDX: 0000000000000000 RSI: ffffffff87d0b324 RDI: ffff888025fd1290
RBP: 0000000000000003 R08: 0000000000000005 R09: 0000000000000005
R10: 0000000000000003 R11: 0000000000000000 R12: ffff8880293ca000
R13: 000000010000ac01 R14: ffff88804ebc4ec0 R15: ffff88804ebc4f00
FS: 0000000000000000(0000) GS:ffff888123ede000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f238680cff8 CR3: 000000005dc94000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 000000000000000b
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: c1 ea 03 shr $0x3,%edx
3: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
7: 0f 85 65 02 00 00 jne 0x272
d: 48 8b 9b 90 06 00 00 mov 0x690(%rbx),%rbx
14: e8 7c a9 39 fa call 0xfa39a995
19: 48 89 da mov %rbx,%rdx
1c: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
23: fc ff df
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 31 02 00 00 jne 0x265
34: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
3b: fc ff df
3e: 48 rex.W
3f: 8b .byte 0x8b


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