System crash via AMD display null dereference
Published Oct 21, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel's AMD display driver allows local users to crash the system through idle-power handling. The AMD display core passes dc to apply_idle_power_optimizations even when dc->clk_mgr is null, and dcn35_apply_idle_power_optimizations then dereferences that pointer. Reachability requires low-privileged local access and an AMD display path that enters idle-power optimization without an initialized clock manager.
Summary
What happened
NULL pointer dereference in the Linux kernel's AMD display driver allows local users to crash the system through idle-power handling. The AMD display core passes dc to apply_idle_power_optimizations even when dc->clk_mgr is null, and dcn35_apply_idle_power_optimizations then dereferences that pointer. Reachability requires low-privileged local access and an AMD display path that enters idle-power optimization without an initialized clock manager.
The record
- CVE
- CVE-2024-49907
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.15
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <3f7e533c10db3d0158709a99e2129ff63add6bcd
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <5ba3fbf75b243b2863a8be9e7c393e003d3b88f3
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <8d54001f8dccd56146973f23f3ab2ba037a21251
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <95d9e0803e51d5a24276b7643b244c7477daf463
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <9641bc4adf8446034e490ed543ae7e9833cfbdf5
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <a2773e0a4b79e7a6463abdffaf8cc4f24428ba18
- Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <a545a9403e04c6e17fdc04a26a61d9feebbba106
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo