From: syzbot <syzbot+listf9a52addc2d8713c0b5e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly media report (Jan 2024)
Date: Wed, 10 Jan 2024 12:36:26 -0800 [thread overview]
Message-ID: <000000000000951e73060e9d627a@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, 1 new issues were detected and 0 were fixed.
In total, 13 issues are still open and 85 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 855 Yes general protection fault in ir_raw_event_store_with_filter
https://syzkaller.appspot.com/bug?extid=34008406ee9a31b13c73
<2> 108 Yes inconsistent lock state in sync_timeline_debug_remove
https://syzkaller.appspot.com/bug?extid=7dcd254b8987a29f6450
<3> 100 Yes WARNING in media_create_pad_link
https://syzkaller.appspot.com/bug?extid=dd320d114deb3f5bb79b
<4> 86 Yes WARNING in smsusb_start_streaming/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=12002a39b8c60510f8fb
<5> 55 Yes KASAN: use-after-free Read in send_packet
https://syzkaller.appspot.com/bug?extid=f1a69784f6efe748c3bf
<6> 3 Yes KASAN: use-after-free Read in em28xx_init_extension (2)
https://syzkaller.appspot.com/bug?extid=99d6c66dbbc484f50e1c
---
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:[~2024-01-10 20:36 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=000000000000951e73060e9d627a@google.com \
--to=syzbot+listf9a52addc2d8713c0b5e@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