Local privilege escalation via pKVM size overflow
Published Mar 2, 2026 · Updated Mar 2, 2026
Integer overflow in Android kernel pKVM allows local users to escalate privileges through a crafted host-to-guest memory-sharing request. __pkvm_host_share_guest in mem_protect.c adds an attacker-controlled address and size without rejecting wraparound, so range validation accepts a truncated end boundary and permits an out-of-bounds write. No prior execution privileges or user interaction are required; successful exploitation grants elevated local control over the device.
Summary
What happened
Integer overflow in Android kernel pKVM allows local users to escalate privileges through a crafted host-to-guest memory-sharing request. __pkvm_host_share_guest in mem_protect.c adds an attacker-controlled address and size without rejecting wraparound, so range validation accepts a truncated end boundary and permits an out-of-bounds write. No prior execution privileges or user interaction are required; successful exploitation grants elevated local control over the device.
The record
- CVE
- CVE-2026-0028
- 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