# CVE-2026-89619: HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer

> A buffer overflow in the Intel THC HID QuickSPI driver allows a malicious device to corrupt kernel memory, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89619, DEBIAN-CVE-2026-89619, GHSA-mjmr-px5q-jfhp, UBUNTU-CVE-2026-89619

## What is CVE-2026-89619?

CVE-2026-89619 is a high-severity memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-89619?


## How do I fix CVE-2026-89619?

Apply the vendor's patch.

## Is CVE-2026-89619 being exploited?

There is no known exploitation of CVE-2026-89619 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89619 and fix it if it is affected.

What it is: CVE-2026-89619 is a high-severity memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89619 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89619/ (Markdown: https://insights.sbomify.com/CVE-2026-89619/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89619
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89619
- OSV: https://osv.dev/vulnerability/CVE-2026-89619

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89619/
Summaries are generated and may contain mistakes; the official description above is the record.