kASLR bypass via faulty memory handling
Published Dec 11, 2024 · Updated Apr 2, 2026
Information disclosure in the macOS kernel before 15.2 allows local users to bypass kASLR through a malicious app. Apple has not published the affected kernel routine or the exact memory-handling operation that exposes the randomized kernel layout. Exploitation requires local low-privilege code execution and reveals address-layout information that can weaken kernel exploit mitigations.
Summary
What happened
Information disclosure in the macOS kernel before 15.2 allows local users to bypass kASLR through a malicious app. Apple has not published the affected kernel routine or the exact memory-handling operation that exposes the randomized kernel layout. Exploitation requires local low-privilege code execution and reveals address-layout information that can weaken kernel exploit mitigations.
The record
- CVE
- CVE-2024-54531
- Published
- Dec 11, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- T1211
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 11, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 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=0 <15.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