KASLR bypass via task-stack address disclosure
Published Jan 17, 2025 · Updated Mar 15, 2025
Information disclosure in the Android kernel allows local users with System privileges to bypass KASLR without user interaction. On arm64, thread_info shares the task stack, so a leaked stack address exposes a predictable kernel-structure address and defeats layout randomization. System-level code execution is required; the disclosure reveals kernel layout information but does not directly modify data or interrupt the device.
Summary
What happened
Information disclosure in the Android kernel allows local users with System privileges to bypass KASLR without user interaction. On arm64, thread_info shares the task stack, so a leaked stack address exposes a predictable kernel-structure address and defeats layout randomization. System-level code execution is required; the disclosure reveals kernel layout information but does not directly modify data or interrupt the device.
The record
- CVE
- CVE-2018-9384
- Published
- Jan 17, 2025
- Updated
- Mar 15, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-200
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 17, 2025CVE publishedPublication date reported by the CVE source.
- Mar 15, 2025Record 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=Android Kernel
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