# drm/vmwgfx: Fix KMS with 3D on HW version 10

CVE record · `CVE-2026-23008`

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

Published by the CVE Program (CNA: Linux) at 25 Jan 2026, 14:36 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: `965544150d1cadf0e8f5bb6c13c19697e46e1429 to before a91bdd21d5efb3072beefbec13762b7722200c49` (git)
  - affected: `965544150d1cadf0e8f5bb6c13c19697e46e1429 to before d9186faeae6efb7d0841a5e8eb213ff4c7966614` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.16`
  - unaffected: `before 6.16` (semver)
  - unaffected: `6.18.7 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 from 6.16 up to the fixed releases is affected by a flaw in the vmwgfx DRM driver. On HW version 10 with 3D KMS, a null pointer dereference crashes the driver and causes a black screen. The source gives few details on attacker requirements. Upgrade to 6.18.7 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.0016, the 5th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

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

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/a91bdd21d5efb3072beefbec13762b7722200c49>
- <https://git.kernel.org/stable/c/d9186faeae6efb7d0841a5e8eb213ff4c7966614>

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

---

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