Local privilege escalation via mnh_sm integer overflow
Published Jan 17, 2025 · Updated Mar 14, 2025
Heap overflow in the Android Kernel mnh_sm driver allows local users to gain elevated privileges by triggering an integer overflow. Multiple functions in mnh-sm.c fail to prevent integer overflow, which causes a heap overflow; Google has not disclosed the individual functions or input path. A local user needs no additional execution privileges, and exploitation requires no user interaction; successful exploitation raises privileges.
Summary
What happened
Heap overflow in the Android Kernel mnh_sm driver allows local users to gain elevated privileges by triggering an integer overflow. Multiple functions in mnh-sm.c fail to prevent integer overflow, which causes a heap overflow; Google has not disclosed the individual functions or input path. A local user needs no additional execution privileges, and exploitation requires no user interaction; successful exploitation raises privileges.
The record
- CVE
- CVE-2018-9387
- Published
- Jan 17, 2025
- Updated
- Mar 14, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 17, 2025CVE publishedPublication date reported by the CVE source.
- Mar 14, 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