From: Lee Jones <lee@kernel.org>
To: FirstName LastName <bsevens@google.com>, stable@vger.kernel.org
Cc: Roderick Colenbrander <roderick.colenbrander@sony.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: playstation: validate num_touch_reports in DualShock 4 reports
Date: Mon, 13 Jul 2026 12:24:07 +0100 [thread overview]
Message-ID: <20260713112407.GB3774971@google.com> (raw)
In-Reply-To: <20260713112252.GA3774971@google.com>
[This time with the Stable Team included #fail]
> Stable Team,
>
> > From: Benoît Sevens <bsevens@google.com>
> >
> > The DualShock 4 HID driver fails to validate the num_touch_reports field
> > received from the device in both USB and Bluetooth input reports.
> > A malicious device could set this field to a value larger than the
> > allocated size of the touch_reports array (3 for USB, 4 for Bluetooth),
> > leading to an out-of-bounds read in dualshock4_parse_report().
> >
> > This can result in kernel memory disclosure when processing malicious
> > HID reports.
> >
> > Validate num_touch_reports against the array size for the respective
> > connection types before processing the touch data.
> >
> > Signed-off-by: Benoît Sevens <bsevens@google.com>
> > ---
> > drivers/hid/hid-playstation.c | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
>
> Could we have this in all branches up to and including linux-6.6.y please?
>
> Upstream commit:
>
> Fixes: 82a4fc463309 ("HID: playstation: validate num_touch_reports in DualShock 4 reports")
--
Lee Jones
prev parent reply other threads:[~2026-07-13 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 12:47 [PATCH] HID: playstation: validate num_touch_reports in DualShock 4 reports FirstName LastName
2026-04-09 15:55 ` Jiri Kosina
2026-07-13 11:22 ` Lee Jones
2026-07-13 11:24 ` 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=20260713112407.GB3774971@google.com \
--to=lee@kernel.org \
--cc=bentiss@kernel.org \
--cc=bsevens@google.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roderick.colenbrander@sony.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.