Description
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)
Affected products
linux: linux kernel
References5
- git.kernel.org/stable/c/0961673cc5f0055957aa46f25eb4ef6c07e00165 Patch
- git.kernel.org/stable/c/1bcf63a44381691d6192872801f830ce3250e367 Patch
- git.kernel.org/stable/c/4ade995b9b25b3c6e8dc42c27070340f1358d8c8 Patch
- git.kernel.org/stable/c/0d9f4f202de1522aadc7a827aba0ae92b3d70937
- git.kernel.org/stable/c/dd9699368f37aca4f216857847a46a8a2c289f94
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 10 · as of 8 November 2026
- CWE
- CWE-476
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.