From: syzbot <syzbot+listc9ccb76f5ea0f19f24e9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (May 2026)
Date: Sat, 02 May 2026 05:32:33 -0700 [thread overview]
Message-ID: <69f5eee1.050a0220.3cbe47.001b.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, 84 issues are still open and 421 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 12784 Yes INFO: task hung in lbs_remove_card
https://syzkaller.appspot.com/bug?extid=c99d17aa44dbdba16ad2
<2> 3327 Yes possible deadlock in input_inject_event
https://syzkaller.appspot.com/bug?extid=79c403850e6816dc39cf
<3> 2947 Yes INFO: task hung in usbdev_open (2)
https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
<4> 1845 Yes WARNING in igorplugusb_probe/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=5d7eece664082e0c5c1a
<5> 1766 No KASAN: vmalloc-out-of-bounds Read in kcov_remote_start
https://syzkaller.appspot.com/bug?extid=8a173e13208949931dc7
<6> 1437 Yes KASAN: use-after-free Read in em28xx_init_extension (2)
https://syzkaller.appspot.com/bug?extid=99d6c66dbbc484f50e1c
<7> 1071 Yes WARNING in as102_dvb_dmx_start_feed
https://syzkaller.appspot.com/bug?extid=3825a6102073c418fe41
<8> 1010 Yes KMSAN: kernel-infoleak in i2cdev_ioctl_smbus
https://syzkaller.appspot.com/bug?extid=08b819a87faa6def6dfb
<9> 1005 Yes INFO: task hung in hub_port_init (3)
https://syzkaller.appspot.com/bug?extid=b6f11035e572f08bc20f
<10> 858 No INFO: task hung in hub_event (3)
https://syzkaller.appspot.com/bug?extid=a7edecbf389d11a369d4
---
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-05-02 12: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=69f5eee1.050a0220.3cbe47.001b.GAE@google.com \
--to=syzbot+listc9ccb76f5ea0f19f24e9@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