# drm/ioc32: stop speculation on the drm_compat_ioctl path

CVE record · `CVE-2026-31781`

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

Published by the CVE Program (CNA: Linux) at 1 May 2026, 14:15 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: `505b5240329b922f21f91d5b5d1e535c805eca6d to before 46a60ee8956ef1975f00455f614761c7ecedc09d` (git)
  - affected: `505b5240329b922f21f91d5b5d1e535c805eca6d to before 5bb398991f378ef74d90b14a6ea8b61ff96cc03a` (git)
  - affected: `505b5240329b922f21f91d5b5d1e535c805eca6d to before d59c5d8539662d95887b4564f3f72ad38076a2d5` (git)
  - affected: `505b5240329b922f21f91d5b5d1e535c805eca6d to before 489f2ef2b908898d01df697dc4fe1476674be640` (git)
  - affected: `505b5240329b922f21f91d5b5d1e535c805eca6d to before 4a41c2b18fc05d30b718d2602cac339eae710b34` (git)
  - affected: `505b5240329b922f21f91d5b5d1e535c805eca6d to before f0e441be08a2eab10b2d06fccfa267ee599dd6b3` (git)
  - affected: `505b5240329b922f21f91d5b5d1e535c805eca6d to before 27ef84bba9b9d7b03418c60fbc6069ea0e87b13c` (git)
  - affected: `505b5240329b922f21f91d5b5d1e535c805eca6d to before f8995c2df519f382525ca4bc90553ad2ec611067` (git)
  - affected: `abc60edcfc87771ff244763d4d19c67766f5dd0f` (git)
  - affected: `a2a840d6dcae960c2dfdf3fcb1b759e1b7d90663` (git)
  - affected: `00279b505289f7529d9be2e78915d0483ffbd314` (git)
  - affected: `d04e6ea0cec9e7d6cba806508f657d2d0dc6cacf` (git)
  - and 6 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.20`
  - unaffected: `before 4.20` (semver)
  - unaffected: `5.10.253 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.203 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.168 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.134 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.81 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.22 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.12 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 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 DRM compat ioctl path is affected from version 4.20 until the fixes for each stable branch. A user-controlled pointer is used to index a table of function pointers, a Spectre-style speculation issue, and the source gives few details on attacker requirements. Upgrade to a fixed kernel, such as 5.10.253, 5.15.203, 6.1.168, or 6.6.134 or later in those branches.

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 2nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

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

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/46a60ee8956ef1975f00455f614761c7ecedc09d>
- <https://git.kernel.org/stable/c/5bb398991f378ef74d90b14a6ea8b61ff96cc03a>
- <https://git.kernel.org/stable/c/d59c5d8539662d95887b4564f3f72ad38076a2d5>
- <https://git.kernel.org/stable/c/489f2ef2b908898d01df697dc4fe1476674be640>
- <https://git.kernel.org/stable/c/4a41c2b18fc05d30b718d2602cac339eae710b34>
- <https://git.kernel.org/stable/c/f0e441be08a2eab10b2d06fccfa267ee599dd6b3>
- <https://git.kernel.org/stable/c/27ef84bba9b9d7b03418c60fbc6069ea0e87b13c>
- <https://git.kernel.org/stable/c/f8995c2df519f382525ca4bc90553ad2ec611067>

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-31781>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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