From: syzbot <syzbot+list56ddc892c28a2226dc97@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (Jan 2025)
Date: Fri, 17 Jan 2025 02:35:27 -0800 [thread overview]
Message-ID: <678a326f.050a0220.20d369.005a.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, 1 new issues were detected and 0 were fixed.
In total, 92 issues are still open and 366 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 11028 Yes KASAN: slab-use-after-free Read in hdm_disconnect
https://syzkaller.appspot.com/bug?extid=916742d5d24f6c254761
<2> 2087 Yes KASAN: use-after-free Read in v4l2_fh_init
https://syzkaller.appspot.com/bug?extid=c025d34b8eaa54c571b8
<3> 1905 Yes INFO: task hung in jbd2_journal_commit_transaction (5)
https://syzkaller.appspot.com/bug?extid=3071bdd0a9953bc0d177
<4> 1368 Yes KASAN: use-after-free Read in em28xx_init_extension (2)
https://syzkaller.appspot.com/bug?extid=99d6c66dbbc484f50e1c
<5> 1163 Yes KASAN: invalid-free in dev_free
https://syzkaller.appspot.com/bug?extid=3e563d99e70973c0755c
<6> 1046 Yes INFO: task hung in usbdev_open (2)
https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
<7> 799 Yes possible deadlock in blk_mq_alloc_request
https://syzkaller.appspot.com/bug?extid=ca7d7c797fee31d2b474
<8> 793 Yes KASAN: use-after-free Read in v4l2_fh_open
https://syzkaller.appspot.com/bug?extid=b2391895514ed9ef4a8e
<9> 665 Yes INFO: rcu detected stall in syscall_exit_to_user_mode (2)
https://syzkaller.appspot.com/bug?extid=a68ef3b1f46bc3aced5c
<10> 664 Yes INFO: task hung in hub_port_init (3)
https://syzkaller.appspot.com/bug?extid=b6f11035e572f08bc20f
---
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-01-17 10:35 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=678a326f.050a0220.20d369.005a.GAE@google.com \
--to=syzbot+list56ddc892c28a2226dc97@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.