From: syzbot <syzbot+list431b29af76eb8b41eafb@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (May 2025)
Date: Thu, 22 May 2025 05:58:28 -0700 [thread overview]
Message-ID: <682f1f74.a00a0220.2a3337.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, 6 new issues were detected and 1 were fixed.
In total, 95 issues are still open and 378 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 14709 Yes KASAN: slab-use-after-free Read in hdm_disconnect
https://syzkaller.appspot.com/bug?extid=916742d5d24f6c254761
<2> 9154 Yes WARNING in ath6kl_bmi_get_target_info (2)
https://syzkaller.appspot.com/bug?extid=92c6dd14aaa230be6855
<3> 4164 Yes KASAN: use-after-free Read in v4l2_fh_init
https://syzkaller.appspot.com/bug?extid=c025d34b8eaa54c571b8
<4> 3644 Yes WARNING in plfxlc_mac_release
https://syzkaller.appspot.com/bug?extid=51a42f7c2e399392ea82
<5> 2125 Yes INFO: task hung in jbd2_journal_commit_transaction (5)
https://syzkaller.appspot.com/bug?extid=3071bdd0a9953bc0d177
<6> 1513 Yes WARNING in usb_free_urb
https://syzkaller.appspot.com/bug?extid=b466336413a1fba398a5
<7> 1460 Yes KASAN: use-after-free Read in v4l2_fh_open
https://syzkaller.appspot.com/bug?extid=b2391895514ed9ef4a8e
<8> 1149 Yes INFO: task hung in usbdev_open (2)
https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
<9> 798 Yes INFO: rcu detected stall in syscall_exit_to_user_mode (2)
https://syzkaller.appspot.com/bug?extid=a68ef3b1f46bc3aced5c
<10> 752 Yes WARNING in enable_work
https://syzkaller.appspot.com/bug?extid=7053fbd8757fecbbe492
---
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:[~2025-05-22 12:58 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=682f1f74.a00a0220.2a3337.001b.GAE@google.com \
--to=syzbot+list431b29af76eb8b41eafb@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.