From: Lee Jones <lee@kernel.org>
To: Wenshan Lan <jetlan9@163.com>
Cc: Benjamin Tissoires <bentiss@kernel.org>,
gregkh@linuxfoundation.org, sashal@kernel.org,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.12.y] HID: core: Mitigate potential OOB by removing bogus memset()
Date: Wed, 3 Jun 2026 13:16:32 +0100 [thread overview]
Message-ID: <20260603121632.GB9653@google.com> (raw)
In-Reply-To: <e62974e5-f341-47e5-9563-354df51aa6db@163.com>
On Wed, 03 Jun 2026, Wenshan Lan wrote:
>
> On 6/3/2026 3:04 PM, Benjamin Tissoires wrote:
> > On Jun 03 2026, Wenshan Lan wrote:
> > > From: Lee Jones <lee@kernel.org>
> > >
> > > [ Upstream commit 0a3fe972a7cb1404f693d6f1711f32bc1d244b1c ]
> > >
> > > The memset() in hid_report_raw_event() has the good intention of
> > > clearing out bogus data by zeroing the area from the end of the incoming
> > > data string to the assumed end of the buffer. However, as we have
> > > previously seen, doing so can easily result in OOB reads and writes in
> > > the subsequent thread of execution.
> > >
> > > The current suggestion from one of the HID maintainers is to remove the
> > > memset() and simply return if the incoming event buffer size is not
> > > large enough to fill the associated report.
> > >
> > > Suggested-by Benjamin Tissoires <bentiss@kernel.org>
> > >
> > > Signed-off-by: Lee Jones <lee@kernel.org>
> > > [bentiss: changed the return value]
> > > Signed-off-by: Benjamin Tissoires <bentiss@kernel.org>
> > > [ Replace hid_warn_ratelimited() with hid_warn() in v6.12. ]
> > > Signed-off-by: Wenshan Lan <jetlan9@163.com>
> > > ---
> > This commit is known for breaking devices. You can't backport this
> > without the following 3 fixes:
> > 4d3a2a466b8d ("HID: core: Fix size_t specifier in hid_report_raw_event()")
> > 206342541fc8 ("HID: core: introduce hid_safe_input_report()")
> > 2c85c61d1332 ("HID: pass the buffer size to hid_report_raw_event")
> >
> > Note that this is the same for your 6.6, 6.1 and 5.15 patches.
>
> Thanks for your suggestion, I will send a V2 later.
https://lore.kernel.org/all/20260601083642.908433-1-lee@kernel.org/
--
Lee Jones
prev parent reply other threads:[~2026-06-03 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 5:43 [PATCH 6.12.y] HID: core: Mitigate potential OOB by removing bogus memset() Wenshan Lan
2026-06-03 7:04 ` Benjamin Tissoires
2026-06-03 11:57 ` Wenshan Lan
2026-06-03 12:16 ` Lee Jones [this message]
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=20260603121632.GB9653@google.com \
--to=lee@kernel.org \
--cc=bentiss@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jetlan9@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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