From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89619: HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer
Date: Fri, 11 Sep 2026 21:45:08 +0200 [thread overview]
Message-ID: <2026091137-CVE-2026-89619-e4c9@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer
quickspi_hid_raw_request() receives the caller's buffer length in len, but
quickspi_get_report() never sees it and copies the whole device-supplied
response into buf regardless:
memcpy(buf, qsdev->report_buf, qsdev->report_len);
qsdev->report_len comes from the input report the touch controller returns,
while buf is sized to whatever the caller asked hidraw for through
HIDIOCGFEATURE or HIDIOCGINPUT. A response larger than that overflows buf
with device-controlled content.
The intel-quicki2c sibling already passes the caller length down to
quicki2c_get_report() and validates the response against it before the
copy. Do the same here.
The Linux kernel CVE team has assigned CVE-2026-89619 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit 4138f21115aec3ebae7805ec3407c72d93558023 and fixed in 6.18.50 with commit 72706b44b665679d7d60a488d8776a911f1a93f3
Issue introduced in 6.14 with commit 4138f21115aec3ebae7805ec3407c72d93558023 and fixed in 7.2.4 with commit 54e0bafc0653bdf2a6c5f5f8ad8787a820d98663
Issue introduced in 6.14 with commit 4138f21115aec3ebae7805ec3407c72d93558023 and fixed in 7.3-rc1 with commit 035ec4a71cb8020a927c123bbe75c2f88d614986
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-89619
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/hid/intel-thc-hid/intel-quickspi/quickspi-hid.c
drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c
drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/72706b44b665679d7d60a488d8776a911f1a93f3
https://git.kernel.org/stable/c/54e0bafc0653bdf2a6c5f5f8ad8787a820d98663
https://git.kernel.org/stable/c/035ec4a71cb8020a927c123bbe75c2f88d614986
reply other threads:[~2026-09-11 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2026091137-CVE-2026-89619-e4c9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@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 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.