# CVE-2026-31571: drm/i915: Unlink NV12 planes earlier

Status: published. Published: 2026-04-24. Updated: 2026-11-05.

In the Linux kernel, the following vulnerability has been resolved:

drm/i915: Unlink NV12 planes earlier

unlink_nv12_plane() will clobber parts of the plane state
potentially already set up by plane_atomic_check(), so we
must make sure not to call the two in the wrong order.
The problem happens when a plane previously selected as
a Y plane is now configured as a normal plane by user space.
plane_atomic_check() will first compute the proper plane
state based on the userspace request, and unlink_nv12_plane()
later clears some of the state.

This used to work on account of unlink_nv12_plane() skipping
the state clearing based on the plane visibility. But I removed
that check, thinking it was an impossible situation. Now when
that situation happens unlink_nv12_plane() will just WARN
and proceed to clobber the state.

Rather than reverting to the old way of doing things, I think
it's more clear if we unlink the NV12 planes before we even
compute the new plane state.

(cherry picked from commit 017ecd04985573eeeb0745fa2c23896fb22ee0cc)

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 6a01df2f1b2a3b29721143729a3feff816bc0083; < 70e2eb91cb6310a3508439f6f2539dfffa0abf77 (affected, git); ≥ 6a01df2f1b2a3b29721143729a3feff816bc0083; < 12f3b6cbab8fbeb95097685b40f0147406cf9746 (affected, git); ≥ 6a01df2f1b2a3b29721143729a3feff816bc0083; < bfa71b7a9dc6b5b8af157686e03308291141d00c (affected, git). Source: CNA: Linux
- Linux / Linux: 6.15 (affected); ≥ 0; < 6.15 (unaffected, semver); ≥ 6.18.21; ≤ 6.18.* (unaffected, semver); ≥ 6.19.11; ≤ 6.19.* (unaffected, semver); ≥ 7.0; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.12% as of 2026-11-05; percentile 1.90%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/70e2eb91cb6310a3508439f6f2539dfffa0abf77 (CNA: Linux)

- https://git.kernel.org/stable/c/12f3b6cbab8fbeb95097685b40f0147406cf9746 (CNA: Linux)

- https://git.kernel.org/stable/c/bfa71b7a9dc6b5b8af157686e03308291141d00c (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-31571; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-31571; retrieved 2026-11-05; source updated Not reported

Revision: 23f1256d02984355533e54e3ac092a34ae8f1a4c11999e9d23267de23206bc25

Canonical: https://y2.dev/cve/CVE-2026-31571

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.