Local privilege escalation via function-pointer bounds check
Published Dec 5, 2024 · Updated Dec 6, 2024
Out-of-bounds read in the Android Kernel allows local users with System privileges to elevate execution through the wlanThermo procfs entry. procfile_write in gl_proc.c applies an incorrect bounds check before reading a function pointer, allowing the read to cross its intended boundary. Exploitation requires local System execution privileges, needs no user interaction, and can elevate code into a more privileged context.
Summary
What happened
Out-of-bounds read in the Android Kernel allows local users with System privileges to elevate execution through the wlanThermo procfs entry. procfile_write in gl_proc.c applies an incorrect bounds check before reading a function pointer, allowing the read to cross its intended boundary. Exploitation requires local System execution privileges, needs no user interaction, and can elevate code into a more privileged context.
The record
- CVE
- CVE-2018-9390
- Published
- Dec 5, 2024
- Updated
- Dec 6, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-125, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 5, 2024CVE publishedPublication date reported by the CVE source.
- Dec 6, 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=kernel
- Affected versionversion=Kernel
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.
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