Answer in brief
CVE-2026-31571 records a Unknown severity vulnerability in drm/i915: Unlink NV12 planes earlier. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6a01df2f1b2a3b29721143729a3feff816bc0083 <70e2eb91cb6310a3508439f6f2539dfffa0abf77 || >=6a01df2f1b2a3b29721143729a3feff816bc0083 <12f3b6cbab8fbeb95097685b40f0147406cf9746 || >=6a01df2f1b2a3b29721143729a3feff816bc0083 <bfa71b7a9dc6b5b8af157686e03308291141d00c | 70e2eb91cb6310a3508439f6f2539dfffa0abf77, 12f3b6cbab8fbeb95097685b40f0147406cf9746, bfa71b7a9dc6b5b8af157686e03308291141d00c |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.