KASLR bypass via arbitrary free after use
Published Nov 15, 2021 · Updated Sep 17, 2024
Use-after-free in AMD Radeon Software before 20.11.2 allows local users to bypass KASLR or disclose kernel information through the Windows driver. AMD's bulletin attributes the flaw to arbitrary free-after-use handling in AMD Escape calls but does not identify the specific handler or object lifecycle. Exploitation requires local access to the Windows graphics driver; the stated consequences are information disclosure and KASLR bypass, with no documented data modification or service interruption.
Summary
What happened
Use-after-free in AMD Radeon Software before 20.11.2 allows local users to bypass KASLR or disclose kernel information through the Windows driver. AMD's bulletin attributes the flaw to arbitrary free-after-use handling in AMD Escape calls but does not identify the specific handler or object lifecycle. Exploitation requires local access to the Windows graphics driver; the stated consequences are information disclosure and KASLR bypass, with no documented data modification or service interruption.
The record
- CVE
- CVE-2020-12901
- Published
- Nov 15, 2021
- Updated
- Sep 17, 2024
- Vendor
- AMD
- Product
- Radeon Software
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 15, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record 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=Radeon Pro Software for Enterprise <21.Q2
- Affected versionversion=Radeon Software <20.11.2
What conditions does exploitation require?
What is affected?
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