[v6.1] BUG: unable to handle kernel paging request in dummy_set_selfpowered

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dc5c83b7f5f8 Linux 6.1.178
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1460dca9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link: https://syzkaller.appspot.com/bug?extid=221ed22d6b6d69b8f53f
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/96393e4697a3/disk-dc5c83b7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0d4afce44fab/vmlinux-dc5c83b7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4787e310d875/Image-dc5c83b7.gz.xz

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

Mass Storage Function, version: 2009/09/11
LUN: removable file: (no medium)
Unable to handle kernel paging request at virtual address dfff800000000000
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000000] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 6060 Comm: syz.4.527 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : dummy_set_selfpowered+0xb0/0x158 drivers/usb/gadget/udc/dummy_hcd.c:887
lr : gadget_to_dummy_hcd drivers/usb/gadget/udc/dummy_hcd.c:316 [inline]
lr : dummy_set_selfpowered+0x80/0x158 drivers/usb/gadget/udc/dummy_hcd.c:887
sp : ffff800021577570
x29: ffff800021577570 x28: 1fffe0001e54ec95 x27: 1fffe0001a49b18b
x26: dfff800000000000 x25: ffff0000f59d2910 x24: ffff0000f59d2948
x23: ffff0000f2a76510 x22: dfff800000000000 x21: 0000000000000003
x20: 0000000000000000 x19: 0000000000000001 x18: 0000000000000000
x17: ffff8000089b57b8 x16: ffff800011b90540 x15: ffff8000089b6114
x14: 0000000000000001 x13: 1fffe0001800461b x12: 0000000000080000
x11: ff0080000dceb90c x10: 0000000000000002 x9 : 0000000000000658
x8 : 0000000000000000 x7 : ffff800008bdbb1c x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082d66b0
x2 : 0000000000000001 x1 : 0000000000000003 x0 : 0000000000000005
Call trace:
dummy_set_selfpowered+0xb0/0x158 drivers/usb/gadget/udc/dummy_hcd.c:887
usb_gadget_set_selfpowered+0x70/0x388 drivers/usb/gadget/udc/core.c:578
composite_dev_prepare+0x28c/0x2bc drivers/usb/gadget/composite.c:2338
configfs_composite_bind+0xa0/0xce4 drivers/usb/gadget/configfs.c:1302
gadget_bind_driver+0x26c/0x684 drivers/usb/gadget/udc/core.c:1651
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x3a0/0xac4 drivers/base/dd.c:638
__driver_probe_device+0x1c8/0x368 drivers/base/dd.c:804
driver_probe_device+0x78/0x324 drivers/base/dd.c:834
__driver_attach+0x3bc/0x614 drivers/base/dd.c:1220
bus_for_each_dev+0x148/0x1d0 drivers/base/bus.c:303
driver_attach+0x50/0x60 drivers/base/dd.c:1237
bus_add_driver+0x2c0/0x518 drivers/base/bus.c:620
driver_register+0x200/0x37c drivers/base/driver.c:246
usb_gadget_register_driver_owner+0xf0/0x25c drivers/usb/gadget/udc/core.c:1730
gadget_dev_desc_UDC_store+0x168/0x268 drivers/usb/gadget/configfs.c:290
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x260/0x338 fs/configfs/file.c:229
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x3c8/0x7c8 fs/read_write.c:584
ksys_write+0x12c/0x228 fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: aa1403e0 96b0252e f9400294 d343fe88 (38766908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: aa1403e0 mov x0, x20
4: 96b0252e bl 0xfffffffffac094bc
8: f9400294 ldr x20, [x20]
c: d343fe88 lsr x8, x20, #3
* 10: 38766908 ldrb w8, [x8, x22] <-- trapping instruction


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