From: syzbot <syzbot+listc77a48b31fc59287ba96@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (Apr 2025)
Date: Tue, 22 Apr 2025 03:11:35 -0700 [thread overview]
Message-ID: <68076b57.050a0220.8500a.0009.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, 5 new issues were detected and 0 were fixed.
In total, 89 issues are still open and 376 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 13990 Yes KASAN: slab-use-after-free Read in hdm_disconnect
https://syzkaller.appspot.com/bug?extid=916742d5d24f6c254761
<2> 8298 Yes WARNING in ath6kl_bmi_get_target_info (2)
https://syzkaller.appspot.com/bug?extid=92c6dd14aaa230be6855
<3> 3819 Yes KASAN: use-after-free Read in v4l2_fh_init
https://syzkaller.appspot.com/bug?extid=c025d34b8eaa54c571b8
<4> 3395 Yes WARNING in plfxlc_mac_release
https://syzkaller.appspot.com/bug?extid=51a42f7c2e399392ea82
<5> 2051 Yes INFO: task hung in jbd2_journal_commit_transaction (5)
https://syzkaller.appspot.com/bug?extid=3071bdd0a9953bc0d177
<6> 1387 Yes KASAN: use-after-free Read in em28xx_init_extension (2)
https://syzkaller.appspot.com/bug?extid=99d6c66dbbc484f50e1c
<7> 1253 Yes KASAN: use-after-free Read in v4l2_fh_open
https://syzkaller.appspot.com/bug?extid=b2391895514ed9ef4a8e
<8> 1108 Yes INFO: task hung in usbdev_open (2)
https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
<9> 1273 Yes WARNING in usb_free_urb
https://syzkaller.appspot.com/bug?extid=b466336413a1fba398a5
<10> 766 Yes INFO: rcu detected stall in syscall_exit_to_user_mode (2)
https://syzkaller.appspot.com/bug?extid=a68ef3b1f46bc3aced5c
---
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-04-22 10:11 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=68076b57.050a0220.8500a.0009.GAE@google.com \
--to=syzbot+listc77a48b31fc59287ba96@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