public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: "Günther Noack" <gnoack@google.com>
Cc: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] HID: magicmouse: Prevent out-of-bounds (OOB) read during DOUBLE_REPORT_ID
Date: Thu, 30 Apr 2026 15:01:48 +0100	[thread overview]
Message-ID: <20260430140148.GJ1806155@google.com> (raw)
In-Reply-To: <aeDwkQ-S6QQuK_RL@google.com>

On Thu, 16 Apr 2026, Günther Noack wrote:

> On Thu, Apr 16, 2026 at 02:16:54PM +0100, Lee Jones wrote:
> > It is currently possible for a malicious or misconfigured USB device to
> > cause an out-of-bounds (OOB) read when submitting reports using
> > DOUBLE_REPORT_ID by specifying a large report length and providing a
> > smaller one.
> > 
> > Let's prevent that by comparing the specified report length with the
> > actual size of the data read in from userspace.  If the actual data
> > length ends up being smaller than specified, we'll politely warn the
> > user and prevent any further processing.
> > 
> > Signed-off-by: Lee Jones <lee@kernel.org>
> > ---
> > v1 => v2: Add more size checks to protect against issues during recursion
> > 
> >  drivers/hid/hid-magicmouse.c | 16 ++++++++++++++++
> >  1 file changed, 16 insertions(+)
> > 
> > diff --git a/drivers/hid/hid-magicmouse.c b/drivers/hid/hid-magicmouse.c
> > index 91f621ceb924..e84e6b21d113 100644
> > --- a/drivers/hid/hid-magicmouse.c
> > +++ b/drivers/hid/hid-magicmouse.c
> > @@ -390,6 +390,10 @@ static int magicmouse_raw_event(struct hid_device *hdev,
> >  	struct input_dev *input = msc->input;
> >  	int x = 0, y = 0, ii, clicks = 0, npoints;
> >  
> > +	/* Protect against zero sized recursive calls from DOUBLE_REPORT_ID */
> > +	if (size < 1)
> > +		return 0;
> > +
> >  	switch (data[0]) {
> >  	case TRACKPAD_REPORT_ID:
> >  	case TRACKPAD2_BT_REPORT_ID:
> > @@ -490,6 +494,18 @@ static int magicmouse_raw_event(struct hid_device *hdev,
> >  		/* Sometimes the trackpad sends two touch reports in one
> >  		 * packet.
> >  		 */
> > +
> > +		/* Ensure that we have at least 2 elements (report type and size) */
> > +		if (size < 2)
> > +			return 0;
> > +
> > +		if (size < data[1] + 2) {
> > +			hid_warn(hdev,
> > +				 "received report length (%d) was smaller than specified (%d)",
> > +				 size, data[1] + 2);
> > +			return 0;
> > +		}
> > +
> >  		magicmouse_raw_event(hdev, report, data + 2, data[1]);
> >  		magicmouse_raw_event(hdev, report, data + 2 + data[1],
> >  			size - 2 - data[1]);
> > -- 
> > 2.54.0.rc1.513.gad8abe7a5a-goog
> > 
> 
> Thank you! This looks correct now.
> 
> Reviewed-by: Günther Noack <gnoack@google.com>

Contentless ping. =:-)

-- 
Lee Jones

      reply	other threads:[~2026-04-30 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 13:16 [PATCH v2 1/1] HID: magicmouse: Prevent out-of-bounds (OOB) read during DOUBLE_REPORT_ID Lee Jones
2026-04-16 14:22 ` Günther Noack
2026-04-30 14:01   ` 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=20260430140148.GJ1806155@google.com \
    --to=lee@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=gnoack@google.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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