Local privilege escalation via overflowing HVC ranges
Published Mar 2, 2026 · Updated Mar 2, 2026
Integer overflow in pKVM mem_protect.c in the Android kernel allows local users to gain elevated privileges through malformed HVC ranges. Multiple memory-protection HVC handlers calculate an end boundary without rejecting size overflow, so a wrapped range can pass validation and drive an out-of-bounds write. Exploitation requires local access but no additional execution privileges or user interaction, and successful corruption yields privilege escalation.
Summary
What happened
Integer overflow in pKVM mem_protect.c in the Android kernel allows local users to gain elevated privileges through malformed HVC ranges. Multiple memory-protection HVC handlers calculate an end boundary without rejecting size overflow, so a wrapped range can pass validation and drive an out-of-bounds write. Exploitation requires local access but no additional execution privileges or user interaction, and successful corruption yields privilege escalation.
The record
- CVE
- CVE-2026-0031
- Published
- Mar 2, 2026
- Updated
- Mar 2, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-190, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2026CVE publishedPublication date reported by the CVE source.
- Mar 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=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