From: syzbot <syzbot+list4790484fe82e35fffc4a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (Jun 2026)
Date: Tue, 02 Jun 2026 13:32:27 -0700 [thread overview]
Message-ID: <6a1f3ddb.7b89b7e1.205e57.000a.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, 3 new issues were detected and 2 were fixed.
In total, 63 issues are still open and 423 have already been fixed.
There are also 19 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3774 Yes possible deadlock in input_inject_event
https://syzkaller.appspot.com/bug?extid=79c403850e6816dc39cf
<2> 1812 Yes WARNING in enable_work
https://syzkaller.appspot.com/bug?extid=7053fbd8757fecbbe492
<3> 1442 Yes KASAN: use-after-free Read in em28xx_init_extension (2)
https://syzkaller.appspot.com/bug?extid=99d6c66dbbc484f50e1c
<4> 1064 Yes KASAN: slab-use-after-free Read in v4l2_open
https://syzkaller.appspot.com/bug?extid=1a7507a194fff09e5c44
<5> 866 No INFO: task hung in hub_event (3)
https://syzkaller.appspot.com/bug?extid=a7edecbf389d11a369d4
<6> 403 Yes INFO: task hung in get_bMaxPacketSize0
https://syzkaller.appspot.com/bug?extid=f7ac46d91cf13b4591a4
<7> 345 No KASAN: slab-use-after-free Read in __usb_hcd_giveback_urb (2)
https://syzkaller.appspot.com/bug?extid=7f5e98b052c766f47f68
<8> 341 Yes INFO: task hung in dvb_usb_i2c_exit
https://syzkaller.appspot.com/bug?extid=0dcc341ee61fc9e4032f
<9> 201 Yes WARNING in cm109_input_open/usb_submit_urb (3)
https://syzkaller.appspot.com/bug?extid=ac0f9c4cc1e034160492
<10> 121 Yes INFO: task hung in usbdev_release (2)
https://syzkaller.appspot.com/bug?extid=bfa320b67fcbe2583c6f
---
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-06-02 20:32 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=6a1f3ddb.7b89b7e1.205e57.000a.GAE@google.com \
--to=syzbot+list4790484fe82e35fffc4a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox