Kernel crash via AMD initialization double-free
Published May 17, 2024 · Updated Aug 5, 2026
Double free in AMD GPU power management in Linux 4.9 through 6.7.1 allows local users to trigger a kernel crash during initialization. When a display-clock dependency allocation fails in si_dpm_init, cleanup frees the extended power table, then si_dpm_fini frees the same fields again through the dpm_failed path. Reachability requires the legacy Southern Islands AMD GPU power-management initialization path and an allocation failure; the resulting memory corruption interrupts the host.
Summary
What happened
Double free in AMD GPU power management in Linux 4.9 through 6.7.1 allows local users to trigger a kernel crash during initialization. When a display-clock dependency allocation fails in si_dpm_init, cleanup frees the extended power table, then si_dpm_fini frees the same fields again through the dpm_failed path. Reachability requires the legacy Southern Islands AMD GPU power-management initialization path and an allocation failure; the resulting memory corruption interrupts the host.
The record
- CVE
- CVE-2023-52691
- Published
- May 17, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=841686df9f7d2942cfd94d024b8591fa3f74ef7c <06d95c99d5a4f5accdb79464076efe62e668c706
- Affected versionversion=841686df9f7d2942cfd94d024b8591fa3f74ef7c <2bf47c89bbaca2bae16581ef1b28aaec0ade0334
- Affected versionversion=841686df9f7d2942cfd94d024b8591fa3f74ef7c <ac16667237a82e2597e329eb9bc520d1cf9dff30
- Affected versionversion=841686df9f7d2942cfd94d024b8591fa3f74ef7c <aeed2b4e4a70c7568d4a5eecd6a109713c0dfbf4
- Affected versionversion=841686df9f7d2942cfd94d024b8591fa3f74ef7c <afe9f5b871f86d58ecdc45b217b662227d7890d0
- Affected versionversion=841686df9f7d2942cfd94d024b8591fa3f74ef7c <ca8e2e251c65e5a712f6025e27bd9b26d16e6f4a
- Affected versionversion=841686df9f7d2942cfd94d024b8591fa3f74ef7c <f957a1be647f7fc65926cbf572992ec2747a93f2
- Affected versionversion=841686df9f7d2942cfd94d024b8591fa3f74ef7c <fb1936cb587262cd539e84b34541abb06e42b2f9
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.
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