From: syzbot <syzbot+listeb24060e7e1069a778b6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (Sep 2026)
Date: Fri, 04 Sep 2026 05:33:29 -0700 [thread overview]
Message-ID: <6a9aba99.efa90033.8a9e.0003.GAE@google.com> (raw)
Hello usb maintainers/developers,
This is a 31-day syzbot report for the usb subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/usb
During the period, 39 new issues were detected and 5 were fixed.
In total, 123 issues are still open and 446 have already been fixed.
There are also 51 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7512 Yes WARNING in usb_free_urb
https://syzkaller.appspot.com/bug?extid=b466336413a1fba398a5
<2> 3461 Yes INFO: trying to register non-static key in __vb2_queue_cancel
https://syzkaller.appspot.com/bug?extid=2302c5dc59995fbb8089
<3> 2802 Yes WARNING in usb_stor_msg_common/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=73c662df6e55838c6ac6
<4> 2713 Yes KASAN: slab-use-after-free Read in v4l2_open
https://syzkaller.appspot.com/bug?extid=1a7507a194fff09e5c44
<5> 1833 Yes WARNING in enable_work
https://syzkaller.appspot.com/bug?extid=7053fbd8757fecbbe492
<6> 1157 Yes WARNING in as102_dvb_dmx_start_feed
https://syzkaller.appspot.com/bug?extid=3825a6102073c418fe41
<7> 999 Yes INFO: task hung in hub_event (3)
https://syzkaller.appspot.com/bug?extid=a7edecbf389d11a369d4
<8> 722 Yes general protection fault in f_midi2_free_ep_reqs
https://syzkaller.appspot.com/bug?extid=01a17afb30637396955e
<9> 674 Yes WARNING in usb_ep_enable
https://syzkaller.appspot.com/bug?extid=7b70c4a6021fd49c4151
<10> 494 No KASAN: global-out-of-bounds Read in usb_copy_descriptors
https://syzkaller.appspot.com/bug?extid=debc5c305403f180c01c
---
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 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=6a9aba99.efa90033.8a9e.0003.GAE@google.com \
--to=syzbot+listeb24060e7e1069a778b6@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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.