From: syzbot <syzbot+list6bbccb1b8e29471d8c2f@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly media report (Sep 2026)
Date: Fri, 04 Sep 2026 13:33:39 -0700 [thread overview]
Message-ID: <6a9b2b23.b5d4176b.238c3e.0007.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, 13 new issues were detected and 0 were fixed.
In total, 47 issues are still open and 119 have already been fixed.
There are also 14 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 295 Yes KASAN: slab-use-after-free Read in dvb_frontend_release (3)
https://syzkaller.appspot.com/bug?extid=ae466a728017ec940b41
<2> 165 Yes WARNING in ttusb_dec_send_command
https://syzkaller.appspot.com/bug?extid=ac9880be0b0b1a5f54d6
<3> 79 Yes KASAN: slab-use-after-free Read in rc_dev_uevent
https://syzkaller.appspot.com/bug?extid=237c754233330b2bf565
<4> 21 Yes memory leak in v4l2_ctrl_handler_init_class (3)
https://syzkaller.appspot.com/bug?extid=b1de0d5fd8a15fac11aa
<5> 14 Yes KASAN: slab-use-after-free Write in dvb_device_put
https://syzkaller.appspot.com/bug?extid=d445a71e1c011b592c16
<6> 13 No general protection fault in subdev_open
https://syzkaller.appspot.com/bug?extid=74de6401dbdd377b5746
<7> 12 Yes BUG: corrupted list in az6007_i2c_xfer
https://syzkaller.appspot.com/bug?extid=0192952caa411a3be209
<8> 3 No WARNING in vidtv_start_feed
https://syzkaller.appspot.com/bug?extid=525fda837bd5fc2be560
<9> 2 Yes WARNING in ttusb_dec_start_feed
https://syzkaller.appspot.com/bug?extid=e1dbaae5eefaa2dfbc35
<10> 2 Yes WARNING in v4l2_ctrl_cluster
https://syzkaller.appspot.com/bug?extid=2d417475ba9d6d02cfc9
---
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.
reply other threads:[~2026-09-04 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a9b2b23.b5d4176b.238c3e.0007.GAE@google.com \
--to=syzbot+list6bbccb1b8e29471d8c2f@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
all inboxes | Powered by JetHome®