Kernel crash via incorrect SMU7 function argument
Published Aug 26, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel AMDGPU SMU7 power manager allows local users to crash the system during driver setup. The SMU7 backend initialization path passes hwmgr->backend where smu7_update_edc_leakage_table expects the enclosing pp_hwmgr object, so the callee interprets the backend as that object and dereferences an invalid backend pointer. Reachability requires local access and SMU7-class AMD graphics hardware during AMDGPU power-management initialization; the documented consequence is a kernel crash, with no confidentiality or integrity impact.
Summary
What happened
NULL pointer dereference in the Linux kernel AMDGPU SMU7 power manager allows local users to crash the system during driver setup. The SMU7 backend initialization path passes hwmgr->backend where smu7_update_edc_leakage_table expects the enclosing pp_hwmgr object, so the callee interprets the backend as that object and dereferences an invalid backend pointer. Reachability requires local access and SMU7-class AMD graphics hardware during AMDGPU power-management initialization; the documented consequence is a kernel crash, with no confidentiality or integrity impact.
The record
- CVE
- CVE-2024-43909
- Published
- Aug 26, 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
- Aug 26, 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.9
- Affected versionversion=599a7e9fe1b683d04f889d68f866f5548b1e0239 <09544cd95c688d3041328a4253bd7514972399bb
- Affected versionversion=599a7e9fe1b683d04f889d68f866f5548b1e0239 <1b8aa82b80bd947b68a8ab051d960a0c7935e22d
- Affected versionversion=599a7e9fe1b683d04f889d68f866f5548b1e0239 <37b9df457cbcf095963d18f17d6cb7dfa0a03fce
- Affected versionversion=599a7e9fe1b683d04f889d68f866f5548b1e0239 <7f56f050f02c27ed89cce1ea0c04b34abce32751
- Affected versionversion=599a7e9fe1b683d04f889d68f866f5548b1e0239 <c02c1960c93eede587576625a1221205a68a904f
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