Hello,
syzbot found the following issue on:
HEAD commit: 6e2fd6534337 Linux 5.15.213
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1441f649580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link:
https://syzkaller.appspot.com/bug?extid=21ee040205c30d140c37
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/d7b46606b13d/disk-6e2fd653.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/da120fdeb081/vmlinux-6e2fd653.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3c2643457e3f/bzImage-6e2fd653.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+21ee04...@syzkaller.appspotmail.com
msi2500 3-1:1.0: failed -32, cmd 41, data 608008
usb 3-1: selecting invalid altsetting 1
msi2500 3-1:1.0: failed -32, cmd 43, data 0000
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6742 at drivers/media/common/videobuf2/videobuf2-core.c:1607 vb2_start_streaming+0x36c/0x4a0 drivers/media/common/videobuf2/videobuf2-core.c:1607
Modules linked in:
CPU: 0 PID: 6742 Comm: syz.2.540 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:vb2_start_streaming+0x36c/0x4a0 drivers/media/common/videobuf2/videobuf2-core.c:1607
Code: 6a ff ff ff 89 d1 80 e1 07 80 c1 03 38 c1 7c a5 48 8d bb 40 02 00 00 e8 82 97 32 fb 48 8d 93 40 02 00 00 eb 90 e8 c4 74 ed fa <0f> 0b e9 72 fe ff ff e8 b8 74 ed fa 4c 8d a3 5c 02 00 00 eb 05 e8
RSP: 0018:ffffc90003bb7a30 EFLAGS: 00010287
RAX: ffffffff868b87ec RBX: ffff888020c82b20 RCX: 0000000000080000
RDX: ffffc90005daa000 RSI: 000000000002b373 RDI: 000000000002b374
RBP: 00000000ffffffe0 R08: ffff888020c82b1f R09: 1ffff11004190563
R10: dffffc0000000000 R11: ffffed1004190564 R12: 00000000ffffffe0
R13: dffffc0000000000 R14: 1ffff11004190563 R15: 0000000000000000
FS: 00007fa57be806c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007faa43271e9c CR3: 0000000058e94000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
vb2_core_streamon+0x253/0x380 drivers/media/common/videobuf2/videobuf2-core.c:2108
__vb2_init_fileio+0x97e/0xc50 drivers/media/common/videobuf2/videobuf2-core.c:2678
__vb2_perform_fileio+0x346/0x1580 drivers/media/common/videobuf2/videobuf2-core.c:2754
vb2_fop_read+0x231/0x340 drivers/media/common/videobuf2/videobuf2-v4l2.c:1180
v4l2_read+0x193/0x2b0 drivers/media/v4l2-core/v4l2-dev.c:314
vfs_read+0x2ff/0xd50 fs/read_write.c:483
ksys_read+0x153/0x260 fs/read_write.c:623
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fa57dc28019
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:00007fa57be80028 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007fa57deaffa0 RCX: 00007fa57dc28019
RDX: 0000000000002020 RSI: 0000200000002c00 RDI: 0000000000000004
RBP: 00007fa57dcbf00c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa57deb0038 R14: 00007fa57deaffa0 R15: 00007ffd657ff748
</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