[v6.1] WARNING in dummy_free_request

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16a0f5b9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=742133560ef71aede3d7
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/9a6fe2a54d0f/disk-fb28aa72.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/742b23a1d931/vmlinux-fb28aa72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b3f257c16d2e/bzImage-fb28aa72.xz

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

gadgetfs: suspended from state 3
gadgetfs: disconnected
------------[ cut here ]------------
WARNING: CPU: 0 PID: 10236 at drivers/usb/gadget/udc/dummy_hcd.c:690 dummy_free_request+0x63/0x70 drivers/usb/gadget/udc/dummy_hcd.c:690
Modules linked in:
CPU: 0 PID: 10236 Comm: syz.0.1764 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:dummy_free_request+0x63/0x70 drivers/usb/gadget/udc/dummy_hcd.c:690
Code: 53 fb 48 8b 03 48 39 d8 75 1b e8 58 5a 02 fb 48 89 df 5b 41 5e e9 dd fe 3a fb e8 48 5a 02 fb 0f 0b 5b 41 5e c3 e8 3d 5a 02 fb <0f> 0b eb e1 66 0f 1f 84 00 00 00 00 00 55 41 57 41 56 41 55 41 54
RSP: 0018:ffffc9000c99fbc0 EFLAGS: 00010287
RAX: ffffffff867fd3e3 RBX: ffff888055611800 RCX: 0000000000080000
RDX: ffffc9000ebf9000 RSI: 0000000000035765 RDI: 0000000000035766
RBP: 1ffff110288e518b R08: ffffffff8e210aef R09: 1ffffffff1c4215d
R10: dffffc0000000000 R11: fffffbfff1c4215e R12: ffff888144728068
R13: dffffc0000000000 R14: ffff888144728068 R15: ffff888055611810
FS: 00007fa4067216c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c356e3b CR3: 0000000028d73000 CR4: 00000000003506f0
DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000083
DR3: ffffffffefffff15 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
gadgetfs_unbind+0x1a5/0x2a0 drivers/usb/gadget/legacy/inode.c:1656
gadget_unbind_driver+0x1bb/0x3d0 drivers/usb/gadget/udc/core.c:1702
device_remove drivers/base/dd.c:547 [inline]
__device_release_driver drivers/base/dd.c:1279 [inline]
device_release_driver_internal+0x47d/0x7c0 drivers/base/dd.c:1305
driver_detach+0x1ef/0x2d0 drivers/base/dd.c:1368
bus_remove_driver+0x11c/0x230 drivers/base/bus.c:679
usb_gadget_unregister_driver+0x4a/0x70 drivers/usb/gadget/udc/core.c:1762
dev_release+0x82/0x1f0 drivers/usb/gadget/legacy/inode.c:1194
__fput+0x20a/0x8b0 fs/file_table.c:320
task_work_run+0x1d0/0x260 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa40579e019
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa406721028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: fffffffffffffffd RBX: 00007fa405a26090 RCX: 00007fa40579e019
RDX: 0000000000000000 RSI: 0000200000000a00 RDI: 0000000000000003
RBP: 00007fa40583500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa405a26128 R14: 00007fa405a26090 R15: 00007ffc9acfadf8
</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