From: syzbot <syzbot+lista85d4caaecea173177e8@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly media report (Nov 2026)
Date: Fri, 06 Nov 2026 04:33:49 -0800 [thread overview]
Message-ID: <6aedc92d.a716b02e.a4a62.0003.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, 4 new issues were detected and 0 were fixed.
In total, 50 issues are still open and 128 have already been fixed.
There are also 13 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 472 Yes KASAN: slab-use-after-free Read in em28xx_release_resources
https://syzkaller.appspot.com/bug?extid=16062f26c6480975e5ed
<2> 349 Yes KASAN: slab-use-after-free Read in dvb_frontend_release (3)
https://syzkaller.appspot.com/bug?extid=ae466a728017ec940b41
<3> 198 Yes KASAN: slab-use-after-free Read in rc_dev_uevent
https://syzkaller.appspot.com/bug?extid=237c754233330b2bf565
<4> 157 Yes INFO: trying to register non-static key in as102_stream_ctrl
https://syzkaller.appspot.com/bug?extid=2a3de29133b40e8f69f3
<5> 156 Yes INFO: trying to register non-static key in as102_dvb_dmx_start_feed
https://syzkaller.appspot.com/bug?extid=3f395d8da879a58fb019
<6> 72 Yes WARNING: held lock freed in device_release_driver_internal
https://syzkaller.appspot.com/bug?extid=ed3ed4f52d1fb6a7367d
<7> 33 Yes WARNING in ttusb_start_feed/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=3caf6a60e5f9be12de08
<8> 29 Yes memory leak in v4l2_ctrl_handler_init_class (3)
https://syzkaller.appspot.com/bug?extid=b1de0d5fd8a15fac11aa
<9> 6 No KASAN: slab-use-after-free Read in __video_do_ioctl (2)
https://syzkaller.appspot.com/bug?extid=4a6e6173b1fc7916e950
<10> 6 Yes KASAN: slab-use-after-free Read in v4l2_release (3)
https://syzkaller.appspot.com/bug?extid=34957180b0ed2581edaf
---
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-11-06 12: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=6aedc92d.a716b02e.a4a62.0003.GAE@google.com \
--to=syzbot+lista85d4caaecea173177e8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.