Local privilege escalation via pKVM memcache race
Published Sep 8, 2026 · Updated Sep 8, 2026
A race condition in Android kernel pKVM heap allocation allows local users to escalate privileges through unauthorized memory access. The arm64 pKVM allocator refills a per-CPU memcache without locking while reclaim can access that cache from another CPU, permitting concurrent page-state corruption. A low-privileged local process must win the race; no user interaction is required, and successful exploitation grants higher device privileges.
Summary
What happened
A race condition in Android kernel pKVM heap allocation allows local users to escalate privileges through unauthorized memory access. The arm64 pKVM allocator refills a per-CPU memcache without locking while reclaim can access that cache from another CPU, permitting concurrent page-state corruption. A low-privileged local process must win the race; no user interaction is required, and successful exploitation grants higher device privileges.
The record
- CVE
- CVE-2026-58848
- Published
- Sep 8, 2026
- Updated
- Sep 8, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-362, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 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