From: Alan Stern <stern@rowland.harvard.edu>
To: syzbot <syzbot+fbe9fff1374eefadffb9@syzkaller.appspotmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KMSAN: kernel-usb-infoleak in usbhid_raw_request
Date: Sun, 13 Jul 2025 15:19:34 -0400 [thread overview]
Message-ID: <e8fe21fa-9a2f-4def-b659-063d55a40f3d@rowland.harvard.edu> (raw)
In-Reply-To: <6873a1fd.a70a0220.3b380f.002f.GAE@google.com>
On Sun, Jul 13, 2025 at 05:09:33AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 3f31a806a62e Merge tag 'mm-hotfixes-stable-2025-07-11-16-1..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14725d82580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=76c2fb9aa0954fb8
> dashboard link: https://syzkaller.appspot.com/bug?extid=fbe9fff1374eefadffb9
> compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=118f50f0580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12725d82580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/33ae17bacfc2/disk-3f31a806.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/f476e6d9400a/vmlinux-3f31a806.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/9ae9e3684ea3/bzImage-3f31a806.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+fbe9fff1374eefadffb9@syzkaller.appspotmail.com
>
> microsoft 0003:045E:07DA.0001: unknown main item tag 0x0
> microsoft 0003:045E:07DA.0001: ignoring exceeding usage max
> =====================================================
> BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x5a1/0x2630 drivers/usb/core/urb.c:430
> usb_submit_urb+0x5a1/0x2630 drivers/usb/core/urb.c:430
> usb_start_wait_urb+0xc2/0x320 drivers/usb/core/message.c:59
> usb_internal_control_msg drivers/usb/core/message.c:103 [inline]
> usb_control_msg+0x27c/0x5b0 drivers/usb/core/message.c:154
> usbhid_raw_request+0x4ab/0x690 drivers/hid/usbhid/hid-core.c:-1
> __hid_request+0x2bd/0x500 drivers/hid/hid-core.c:1989
> hidinput_change_resolution_multipliers drivers/hid/hid-input.c:1950 [inline]
Try again, but with Benjamin Tissoires's recent patches.
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/hid c2ca42f190b6
Alan Stern
next prev parent reply other threads:[~2025-07-13 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 14:02 [syzbot] [usb?] KMSAN: kernel-usb-infoleak in usbhid_raw_request syzbot
2025-07-13 12:09 ` syzbot
2025-07-13 19:19 ` Alan Stern [this message]
2025-07-13 21:20 ` syzbot
2025-07-14 1:11 ` Alan Stern
2025-07-14 1:17 ` syzbot
2025-07-14 2:49 ` Hillf Danton
2025-07-14 5:08 ` syzbot
2025-07-14 13:36 ` Alan Stern
2025-07-14 13:32 ` Alan Stern
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=e8fe21fa-9a2f-4def-b659-063d55a40f3d@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+fbe9fff1374eefadffb9@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).