From: syzbot <syzbot+listb516818c4565cc7c4df6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly usb report (Jun 2024)
Date: Mon, 10 Jun 2024 04:56:26 -0700 [thread overview]
Message-ID: <000000000000c26f45061a87d6e1@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, 7 new issues were detected and 2 were fixed.
In total, 76 issues are still open and 338 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3414 Yes KMSAN: uninit-value in dib3000mb_attach (2)
https://syzkaller.appspot.com/bug?extid=c88fc0ebe0d5935c70da
<2> 883 Yes WARNING in ar5523_submit_rx_cmd/usb_submit_urb
https://syzkaller.appspot.com/bug?extid=6101b0c732dea13ea55b
<3> 870 Yes general protection fault in ir_raw_event_store_with_filter
https://syzkaller.appspot.com/bug?extid=34008406ee9a31b13c73
<4> 651 Yes INFO: task hung in usbdev_open (2)
https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
<5> 646 Yes INFO: task hung in hub_port_init (3)
https://syzkaller.appspot.com/bug?extid=b6f11035e572f08bc20f
<6> 406 Yes INFO: task hung in r871xu_dev_remove
https://syzkaller.appspot.com/bug?extid=f39c1dad0b7db49ca4a8
<7> 363 Yes INFO: rcu detected stall in hub_event
https://syzkaller.appspot.com/bug?extid=ec5f884c4a135aa0dbb9
<8> 304 Yes KASAN: use-after-free Read in v4l2_fh_init
https://syzkaller.appspot.com/bug?extid=c025d34b8eaa54c571b8
<9> 302 Yes INFO: rcu detected stall in syscall_exit_to_user_mode (2)
https://syzkaller.appspot.com/bug?extid=a68ef3b1f46bc3aced5c
<10> 277 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:[~2024-06-10 11:56 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=000000000000c26f45061a87d6e1@google.com \
--to=syzbot+listb516818c4565cc7c4df6@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