From: Alan Stern <stern@rowland.harvard.edu>
To: Benjamin Tissoires <bentiss@kernel.org>
Cc: syzbot <syzbot+b63d677d63bcac06cf90@syzkaller.appspotmail.com>,
jikos@kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] HID: core: Reject report fields with a size or count of 0
Date: Mon, 21 Jul 2025 09:56:29 -0400 [thread overview]
Message-ID: <bd033800-53f0-4d5a-a52b-b0e01ac48c12@rowland.harvard.edu> (raw)
In-Reply-To: <voiysrjm3okjtaz7axqupr2jk5yyvxsqgagbwrsey4z24g6rf4@xb75ss3bwol5>
On Mon, Jul 21, 2025 at 03:05:58PM +0200, Benjamin Tissoires wrote:
> > So then would it be better to accept these report fields (perhaps with a
> > warning) and instead, harden the core HID code so that it doesn't choke
> > when it runs across one of them?
> >
>
> Yeah, that seems like the best plan forward.
>
> [sorry on reduced setup for the next 3 weeks, so I can't really debug
> the entire thing now.]
>
> Though, we should probably not annoy users unless we are trying to do
> something that won't be needed. I doubt that Saitek gamepad will ever
> call the faulty functions, so why putting an error in the logs when it's
> working fine?
All right.
Probably the best way to do this is simply to revert the commit that's
already applied and then merge a new patch to harden the core. Would
you like me to post the reversion patch or do you prefer to do it
yourself?
Alan Stern
next prev parent reply other threads:[~2025-07-21 13:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 17:10 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in s32ton (2) syzbot
2025-07-14 18:38 ` Alan Stern
2025-07-14 18:50 ` syzbot
2025-07-14 19:48 ` Alan Stern
2025-07-14 20:28 ` syzbot
2025-07-15 19:29 ` Alan Stern
2025-07-15 19:50 ` syzbot
2025-07-16 14:29 ` Alan Stern
2025-07-16 14:50 ` syzbot
2025-07-16 15:58 ` Alan Stern
2025-07-17 11:48 ` Benjamin Tissoires
2025-07-17 15:10 ` Alan Stern
2025-07-17 15:49 ` syzbot
2025-07-18 2:33 ` [PATCH] HID: core: Reject report fields with a size or count of 0 Alan Stern
2025-07-19 8:36 ` Benjamin Tissoires
2025-07-19 8:40 ` Benjamin Tissoires
2025-07-19 14:48 ` Alan Stern
2025-07-21 13:05 ` Benjamin Tissoires
2025-07-21 13:56 ` Alan Stern [this message]
2025-07-23 9:32 ` Benjamin Tissoires
2025-07-23 14:34 ` Alan Stern
2025-07-23 14:37 ` [PATCH] HID: core: Harden s32ton() against conversion to 0 bits Alan Stern
2025-07-21 14:37 ` [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in s32ton (2) Alan Stern
2025-07-21 15:23 ` syzbot
2025-07-18 16:08 ` (subset) " Benjamin Tissoires
2025-07-23 9:36 ` Benjamin Tissoires
2025-07-25 11:46 ` Benjamin Tissoires
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=bd033800-53f0-4d5a-a52b-b0e01ac48c12@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+b63d677d63bcac06cf90@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
all inboxes | Powered by JetHome®