[syzbot] [media?] WARNING in as102_stream_ctrl

syzbot <[email protected]> Mon, 03 Aug 2026 17:43:21 -0700
Newsgroups org.kernel.vger.linux-media,org.kernel.vger.linux-kernel
Message-ID <[email protected]> 
Hello,

syzbot found the following issue on:

HEAD commit:    075b74841bd0 Linux 7.2-rc6
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1584d3b9580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=145fa60d73086782
dashboard link: https://syzkaller.appspot.com/bug?extid=ea047a32630b1f47da67
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1dc04730d019/disk-075b7484.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d76da42271f4/vmlinux-075b7484.xz
kernel image: https://storage.googleapis.com/syzbot-assets/07b1cdbcbe45/bzImage-075b7484.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: kernel/locking/mutex.c:625 at __mutex_lock_common kernel/locking/mutex.c:625 [inline], CPU#0: syz.0.181/6386
WARNING: kernel/locking/mutex.c:625 at __mutex_lock+0x947/0x1bd0 kernel/locking/mutex.c:821, CPU#0: syz.0.181/6386
Modules linked in:
CPU: 0 UID: 0 PID: 6386 Comm: syz.0.181 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:625 [inline]
RIP: 0010:__mutex_lock+0x94e/0x1bd0 kernel/locking/mutex.c:821
Code: 0f b6 14 11 38 d0 7c 08 84 d2 0f 85 c6 10 00 00 44 8b 35 c5 b6 65 05 45 85 f6 75 13 48 8d 3d a9 14 69 05 48 c7 c6 00 d9 cf 8b <67> 48 0f b9 3a 90 e9 18 f8 ff ff 4d 8d a7 e8 0a 00 00 4c 89 e7 e8
RSP: 0018:ffffc900102cf670 EFLAGS: 00010246
RAX: 0000000000000003 RBX: ffff8880223a6010 RCX: 1ffffffff2245754
RDX: 0000000000000000 RSI: ffffffff8bcfd900 RDI: ffffffff91261890
RBP: ffffc900102cf7e0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS:  00007febfa3f06c0(0000) GS:ffff888123dd8000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007febfa3efff8 CR3: 00000000551cb000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 as102_stream_ctrl+0x28/0xd0 drivers/media/usb/as102/as102_drv.c:259
 dvb_frontend_open+0x220/0x16d0 drivers/media/dvb-core/dvb_frontend.c:2825
 dvb_device_open+0x270/0x3b0 drivers/media/dvb-core/dvbdev.c:109
 chrdev_open+0x234/0x6a0 fs/char_dev.c:411
 do_dentry_open+0x6ab/0x14d0 fs/open.c:947
 vfs_open+0x82/0x3f0 fs/open.c:1052
 do_open fs/namei.c:4700 [inline]
 path_openat+0x2873/0x4280 fs/namei.c:4863
 do_file_open+0x20e/0x430 fs/namei.c:4892
 do_sys_openat2+0x10f/0x1e0 fs/open.c:1368
 do_sys_open fs/open.c:1374 [inline]
 __do_sys_openat fs/open.c:1390 [inline]
 __se_sys_openat fs/open.c:1385 [inline]
 __x64_sys_openat+0x12d/0x210 fs/open.c:1385
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7febfcd5e84e
Code: 08 0f 85 a5 a8 ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 80 00 00 00 00 48 83 ec 08
RSP: 002b:00007febfa3efb28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007febfa3f06c0 RCX: 00007febfcd5e84e
RDX: 0000000000000800 RSI: 00007febfa3efc00 RDI: ffffffffffffff9c
RBP: 00007febfa3efc00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: cccccccccccccccd
R13: 00007febfd0264e8 R14: 00007febfd026450 R15: 00007ffd17b66708
 </TASK>
----------------
Code disassembly (best guess):
   0:	0f b6 14 11          	movzbl (%rcx,%rdx,1),%edx
   4:	38 d0                	cmp    %dl,%al
   6:	7c 08                	jl     0x10
   8:	84 d2                	test   %dl,%dl
   a:	0f 85 c6 10 00 00    	jne    0x10d6
  10:	44 8b 35 c5 b6 65 05 	mov    0x565b6c5(%rip),%r14d        # 0x565b6dc
  17:	45 85 f6             	test   %r14d,%r14d
  1a:	75 13                	jne    0x2f
  1c:	48 8d 3d a9 14 69 05 	lea    0x56914a9(%rip),%rdi        # 0x56914cc
  23:	48 c7 c6 00 d9 cf 8b 	mov    $0xffffffff8bcfd900,%rsi
* 2a:	67 48 0f b9 3a       	ud1    (%edx),%rdi <-- trapping instruction
  2f:	90                   	nop
  30:	e9 18 f8 ff ff       	jmp    0xfffff84d
  35:	4d 8d a7 e8 0a 00 00 	lea    0xae8(%r15),%r12
  3c:	4c 89 e7             	mov    %r12,%rdi
  3f:	e8                   	.byte 0xe8


---
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 [email protected].

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