From: syzbot <syzbot+list844890cacd1fd70d3d36@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly media report (Mar 2026)
Date: Tue, 03 Mar 2026 00:07:26 -0800 [thread overview]
Message-ID: <69a696be.050a0220.21ae90.0009.GAE@google.com> (raw)
Hello media maintainers/developers,
This is a 31-day syzbot report for the media subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/media
During the period, 8 new issues were detected and 1 were fixed.
In total, 32 issues are still open and 103 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2684 Yes KASAN: slab-use-after-free Read in dvb_device_open
https://syzkaller.appspot.com/bug?extid=1eb177ecc3943b883f0a
<2> 451 Yes KASAN: slab-use-after-free Read in em28xx_release_resources
https://syzkaller.appspot.com/bug?extid=16062f26c6480975e5ed
<3> 340 Yes KMSAN: uninit-value in dvbdmx_release_ts_feed
https://syzkaller.appspot.com/bug?extid=01d4620886bee3db0e74
<4> 137 No KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer (4)
https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89
<5> 124 Yes general protection fault in dvb_usbv2_generic_write
https://syzkaller.appspot.com/bug?extid=f9f5333782a854509322
<6> 120 No KASAN: slab-use-after-free Write in as102_release (2)
https://syzkaller.appspot.com/bug?extid=47321e8fd5a4c84088db
<7> 111 Yes general protection fault in vidtv_psi_desc_assign
https://syzkaller.appspot.com/bug?extid=1f5bcc7c919ec578777a
<8> 34 No general protection fault in vidtv_psi_ts_psi_write_into
https://syzkaller.appspot.com/bug?extid=814c351d094f4f1a1b86
<9> 11 Yes BUG: corrupted list in az6007_i2c_xfer
https://syzkaller.appspot.com/bug?extid=0192952caa411a3be209
<10> 4 Yes KASAN: slab-use-after-free Read in v4l2_release (2)
https://syzkaller.appspot.com/bug?extid=a658d41cf8564471775e
---
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 syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
next reply other threads:[~2026-03-03 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 8:07 syzbot [this message]
2026-03-06 16:13 ` [syzbot] Monthly media report (Mar 2026) Nicolas Dufresne
2026-03-10 9:57 ` Pimyn Girgis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69a696be.050a0220.21ae90.0009.GAE@google.com \
--to=syzbot+list844890cacd1fd70d3d36@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox