Answer in brief
CVE-2025-39705 records a Unknown severity vulnerability in drm/amd/display: fix a Null pointer dereference vulnerability. 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 | >=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <0d9f4f202de1522aadc7a827aba0ae92b3d70937 || >=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <0961673cc5f0055957aa46f25eb4ef6c07e00165 || >=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <4ade995b9b25b3c6e8dc42c27070340f1358d8c8 || >=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <1bcf63a44381691d6192872801f830ce3250e367 | 0d9f4f202de1522aadc7a827aba0ae92b3d70937, 0961673cc5f0055957aa46f25eb4ef6c07e00165, 4ade995b9b25b3c6e8dc42c27070340f1358d8c8, 1bcf63a44381691d6192872801f830ce3250e367 |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix a Null pointer dereference vulnerability [Why] A null pointer dereference vulnerability exists in the AMD display driver's (DC module) cleanup function dc_destruct(). When display control context (dc->ctx) construction fails (due to memory allocation failure), this pointer remains NULL. During subsequent error handling when dc_destruct() is called, there's no NULL check before dereferencing the perf_trace member (dc->ctx->perf_trace), causing a kernel null pointer dereference crash. [How] Check if dc->ctx is non-NULL before dereferencing. (Updated commit text and removed unnecessary error message) (cherry picked from commit 9dd8e2ba268c636c240a918e0a31e6feaee19404)
Quoted source text, attributed separately from HOL analysis.