Hello,
syzbot found the following issue on:
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=120ca1d6580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link:
https://syzkaller.appspot.com/bug?extid=763a11951983705d8ec7
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+763a11...@syzkaller.appspotmail.com
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 1 PID: 14165 at kernel/locking/mutex.c:575 __mutex_lock_common+0x195d/0x2400 kernel/locking/mutex.c:-1
Modules linked in:
CPU: 1 PID: 14165 Comm: syz.0.2242 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:__mutex_lock_common+0x195d/0x2400 kernel/locking/mutex.c:575
Code: 00 48 8d bc 24 e0 00 00 00 0f 85 e3 e7 ff ff 48 c7 c7 80 16 2b 8a 48 c7 c6 c0 16 2b 8a e8 6b 83 ec ff 48 8d bc 24 e0 00 00 00 <0f> 0b e9 c1 e7 ff ff e8 17 87 3b f7 e9 00 fc ff ff 0f 0b e9 40 f0
RSP: 0018:ffffc900031cfa60 EFLAGS: 00010246
RAX: c79d88e92803be00 RBX: dffffc0000000000 RCX: 0000000000080000
RDX: ffffc9000590a000 RSI: 000000000000c62f RDI: ffffc900031cfb40
RBP: ffffc900031cfbe8 R08: ffff8880b912795b R09: 1ffff11017224f2b
R10: dffffc0000000000 R11: ffffed1017224f2c R12: 0000000000000000
R13: 1ffff92000639f64 R14: ffffffff86ce1d0c R15: 0000000000000000
FS: 00007f747d5236c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000404030 CR3: 0000000055fe4000 CR4: 00000000003526f0
DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000080083
DR3: ffffffffefffff16 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_interruptible_nested+0x17/0x20 kernel/locking/mutex.c:765
as102_dvb_dmx_start_feed+0x6c/0x280 drivers/media/usb/as102/as102_drv.c:139
dmx_section_feed_start_filtering+0x4f1/0x690 drivers/media/dvb-core/dvb_demux.c:983
dvb_dmxdev_filter_start+0xc87/0x1090 drivers/media/dvb-core/dmxdev.c:766
dvb_demux_do_ioctl+0x463/0x530 drivers/media/dvb-core/dmxdev.c:1077
dvb_usercopy+0x191/0x2b0 drivers/media/dvb-core/dvbdev.c:1017
dvb_demux_ioctl+0x25/0x30 drivers/media/dvb-core/dmxdev.c:1195
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
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:0x7f747f2c9799
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:00007f747d523028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f747f542fa0 RCX: 00007f747f2c9799
RDX: 0000200000000200 RSI: 00000000403c6f2b RDI: 0000000000000004
RBP: 00007f747f35fc99 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f747f543038 R14: 00007f747f542fa0 R15: 00007ffcff466748
</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