[syzbot] [media?] WARNING in vb2_video_unregister_device

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4477a78374a5 Add linux-next specific files for 20260814
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15cda679580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5042554017b3879d
dashboard link: https://syzkaller.appspot.com/bug?extid=f26bc23e42eeb548dee1
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/d1a5728edb0d/disk-4477a783.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3aebe8202fcd/vmlinux-4477a783.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7e9f7367a2bd/bzImage-4477a783.xz

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

usb 3-1: Decoder not found
em28xx 3-1:1.0: failed to create media graph
em28xx 3-1:1.0: V4L2 device radio0 deregistered
------------[ cut here ]------------
!vdev->queue
WARNING: drivers/media/common/videobuf2/videobuf2-v4l2.c:1264 at vb2_video_unregister_device+0x1f8/0x200 drivers/media/common/videobuf2/videobuf2-v4l2.c:1264, CPU#1: kworker/1:1/44
Modules linked in:
CPU: 1 UID: 0 PID: 44 Comm: kworker/1:1 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: events request_module_async
RIP: 0010:vb2_video_unregister_device+0x1f8/0x200 drivers/media/common/videobuf2/videobuf2-v4l2.c:1264
Code: c6 28 4c 89 f0 48 c1 e8 03 80 3c 28 00 4c 8b 24 24 74 08 4c 89 f7 e8 97 0b 09 fa 49 c7 06 00 00 00 00 eb a6 e8 49 90 9a f9 90 <0f> 0b 90 e9 ae fe ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90000b47990 EFLAGS: 00010293
RAX: ffffffff882d4ce7 RBX: 1ffff1100581b29b RCX: ffff888020ec9f40
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffff88802c0d953f R09: 1ffff1100581b2a7
R10: dffffc0000000000 R11: ffffed100581b2a8 R12: ffff88802bb40c00
R13: ffff88802c0d8000 R14: ffff88802c0d94d8 R15: ffff88802c0d8f38
FS: 0000000000000000(0000) GS:ffff8881249ab000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9b1ded3000 CR3: 000000000ed48000 CR4: 00000000003526f0
Call Trace:
<TASK>
em28xx_v4l2_init+0x1c39/0x3150 drivers/media/usb/em28xx/em28xx-video.c:3085
em28xx_init_extension+0x120/0x1d0 drivers/media/usb/em28xx/em28xx-core.c:1248
process_one_work kernel/workqueue.c:3387 [inline]
process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3470
worker_thread+0xa47/0xfb0 kernel/workqueue.c:3551
kthread+0x38b/0x480 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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