[v6.1] WARNING in firmware_fallback_sysfs (2)

[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=101a7e32580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=88ad674700b1b2130bf6
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+88ad67...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 2313 at drivers/base/firmware_loader/fallback.c:144 fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:144 [inline]
WARNING: CPU: 1 PID: 2313 at drivers/base/firmware_loader/fallback.c:144 firmware_fallback_sysfs+0x71e/0x950 drivers/base/firmware_loader/fallback.c:234
Modules linked in:
CPU: 1 PID: 2313 Comm: pvrusb2-context Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:144 [inline]
RIP: 0010:firmware_fallback_sysfs+0x71e/0x950 drivers/base/firmware_loader/fallback.c:234
Code: df e8 36 6a f9 ff 45 89 e7 eb bc e8 bc 01 67 fc c6 05 14 75 f1 08 01 48 c7 c7 20 06 04 8b e8 79 b9 09 05 eb a7 e8 a2 01 67 fc <0f> 0b 4c 89 f7 48 c7 c6 00 07 04 8b 4c 89 e2 e8 83 ba 0d 05 eb 8c
RSP: 0018:ffffc90005e37760 EFLAGS: 00010293
RAX: ffffffff851b2c7e RBX: dffffc0000000000 RCX: ffff8880299fbc00
RDX: 0000000000000000 RSI: 00000000fffffff5 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff90b10367 R09: 1ffffffff216206c
R10: dffffc0000000000 R11: fffffbfff216206d R12: ffffffff8b5f96a0
R13: 0000000000001770 R14: ffff88807bb930a8 R15: 00000000fffffff5
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000002000 CR3: 000000002f072000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
_request_firmware+0xccb/0x1280 drivers/base/firmware_loader/main.c:884
request_firmware+0x32/0x50 drivers/base/firmware_loader/main.c:933
pvr2_locate_firmware+0xb3/0x500 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:1359
pvr2_upload_firmware1+0x1ba/0x940 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:1426
pvr2_hdw_setup_low drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2107 [inline]
pvr2_hdw_setup drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2261 [inline]
pvr2_hdw_initialize+0x422/0x3c10 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2338
pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:111 [inline]
pvr2_context_thread_func+0x4f8/0xbd0 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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