From: syzbot <syzbot+listd6f341b8c90a4c1bdad0@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly media report (Oct 2025)
Date: Mon, 27 Oct 2025 05:50:24 -0700 [thread overview]
Message-ID: <68ff6a90.050a0220.3344a1.0394.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, 2 new issues were detected and 0 were fixed.
In total, 22 issues are still open and 97 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 394 No KASAN: slab-use-after-free Read in em28xx_release_resources
https://syzkaller.appspot.com/bug?extid=16062f26c6480975e5ed
<2> 392 Yes KASAN: slab-use-after-free Read in dvb_device_open
https://syzkaller.appspot.com/bug?extid=1eb177ecc3943b883f0a
<3> 84 Yes general protection fault in su3000_i2c_transfer
https://syzkaller.appspot.com/bug?extid=d99f3a288cc7d8ef60fb
<4> 57 Yes general protection fault in dvb_usbv2_generic_write
https://syzkaller.appspot.com/bug?extid=f9f5333782a854509322
<5> 53 No KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer (4)
https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89
<6> 3 No WARNING in dtv5100_i2c_msg
https://syzkaller.appspot.com/bug?extid=a83ee2dae0e6cc6cd3aa
---
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:[~2025-10-27 12:50 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=68ff6a90.050a0220.3344a1.0394.GAE@google.com \
--to=syzbot+listd6f341b8c90a4c1bdad0@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®