# HID: Intel-thc-hid: Intel-thc: Add safety check for reading DMA buffer

CVE record · `CVE-2026-23196`

- **Identifiers:** `CVE-2026-23196`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 14 Feb 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 14 Feb 2026, 16:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `4138f21115aec3ebae7805ec3407c72d93558023 to before 1e84a807c98a71f767fd1f609637bc5944f916cb` (git)
  - affected: `4138f21115aec3ebae7805ec3407c72d93558023 to before a9a917998d172ec117f9e9de1919174153c0ace4` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.14`
  - unaffected: `before 6.14` (semver)
  - unaffected: `6.18.10 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's HID Intel-thc-hid driver is affected in version 6.14, and earlier versions are not. The source gives few details on how it can be triggered or what an attacker could do beyond causing a NULL pointer access when reading a DMA buffer. Upgrade to 6.18.10 or later in the 6.18 series, or to 6.19 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 14 Feb 2026, 16:27 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-23196)
- 14 Feb 2026, 17:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-23196)

## Sources

- [CVE List: CVE-2026-23196](https://www.cve.org/CVERecord?id=CVE-2026-23196)
- [NVD: CVE-2026-23196](https://nvd.nist.gov/vuln/detail/CVE-2026-23196)

### References from the CNA

- <https://git.kernel.org/stable/c/1e84a807c98a71f767fd1f609637bc5944f916cb>
- <https://git.kernel.org/stable/c/a9a917998d172ec117f9e9de1919174153c0ace4>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-23196>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-23196/>. Everything for agents: <https://agentprime.io/llms.txt>.
