drm/amd/display: fix a Null pointer dereference vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.44, 6.16.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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)
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c · fixed in 0d9f4f202de1522aadc7a827aba0ae92b3d70937; From 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c · fixed in 0961673cc5f0055957aa46f25eb4ef6c07e00165; From 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c · fixed in 4ade995b9b25b3c6e8dc42c27070340f1358d8c8; From 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c · fixed in 1bcf63a44381691d6192872801f830ce3250e367
- Linux Linux
4.15
- KernelLinux
From 4.15.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.44; From 6.13.0 · fixed in 6.16.4