public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	 stable <stable@kernel.org>
Subject: Re: [PATCH] Input: xpad - reject short Xbox One packets before len-relative share-button index
Date: Sun, 26 Apr 2026 21:22:21 -0700	[thread overview]
Message-ID: <ae7kWV1Km1qoEeq3@google.com> (raw)
In-Reply-To: <2026042014-freestyle-deluxe-48e4@gregkh>

Hi Greg,

On Mon, Apr 20, 2026 at 05:53:15PM +0200, Greg Kroah-Hartman wrote:
> xpadone_process_packet() receives len directly from urb->actual_length
> and uses it to index the share-button byte at data[len - 18] or
> data[len - 26].  Since both len and data[0] are under the device's
> control, a broken controller can send a GIP_CMD_INPUT packet with
> actual_length < 18 (e.g. 5 bytes) and reach this code path, causing
> accesses beyond the actual array.
> 
> Since len is u32, 5 - 26 wraps to 0xFFFFFFEB, and data[0xFFFFFFEB] can
> dereference about 4 GiB past the 64-byte usb_alloc_coherent() idata
> buffer.  On a KASAN system this is an immediate splat otherwise the read
> will either fault on an unmapped page (DoS) or pull a bit from arbitrary
> kernel memory and report it as KEY_RECORD.
> 
> Fix this all up by properly bounds checking the value provided by the
> device.
> 
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Fixes: 4ef46367073b ("Input: xpad - fix Share button on Xbox One controllers")
> Cc: stable <stable@kernel.org>
> Assisted-by: gkh_clanker_t1000
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>  drivers/input/joystick/xpad.c | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
> index d6fc3d6006bb..7d99fe0ecf91 100644
> --- a/drivers/input/joystick/xpad.c
> +++ b/drivers/input/joystick/xpad.c
> @@ -1110,10 +1110,13 @@ static void xpadone_process_packet(struct usb_xpad *xpad, u16 cmd, unsigned char
>  		input_report_key(dev, BTN_START,  data[4] & BIT(2));
>  		input_report_key(dev, BTN_SELECT, data[4] & BIT(3));
>  		if (xpad->mapping & MAP_SHARE_BUTTON) {
> -			if (xpad->mapping & MAP_SHARE_OFFSET)
> -				input_report_key(dev, KEY_RECORD, data[len - 26] & BIT(0));
> -			else
> -				input_report_key(dev, KEY_RECORD, data[len - 18] & BIT(0));
> +			if (xpad->mapping & MAP_SHARE_OFFSET) {
> +				if (len >= 26)
> +					input_report_key(dev, KEY_RECORD, data[len - 26] & BIT(0));
> +			} else {
> +				if (len >= 18)
> +					input_report_key(dev, KEY_RECORD, data[len - 18] & BIT(0));
> +			}

Thank you for the report, but this is quite ugly. I committed an
alternative version of the fix.

Thanks.

-- 
Dmitry

  reply	other threads:[~2026-04-27  4:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 15:53 [PATCH] Input: xpad - reject short Xbox One packets before len-relative share-button index Greg Kroah-Hartman
2026-04-27  4:22 ` Dmitry Torokhov [this message]
2026-04-27 11:15   ` Greg Kroah-Hartman

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=ae7kWV1Km1qoEeq3@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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