Local privilege escalation via unchecked VPU mapping
Published Feb 5, 2026 · Updated Feb 5, 2026
Local privilege escalation in the VPU driver in Google Android allows local users to gain elevated privileges through an arbitrary-address mapping. The vpu_mmap handler in vpu_ioctl accepts a mapping request without the bounds check needed to prevent attacker-controlled addresses from being mapped. Exploitation requires local code execution on a supported Pixel device, but needs neither additional execution privileges nor user interaction.
Summary
What happened
Local privilege escalation in the VPU driver in Google Android allows local users to gain elevated privileges through an arbitrary-address mapping. The vpu_mmap handler in vpu_ioctl accepts a mapping request without the bounds check needed to prevent attacker-controlled addresses from being mapped. Exploitation requires local code execution on a supported Pixel device, but needs neither additional execution privileges nor user interaction.
The record
- CVE
- CVE-2026-0106
- Published
- Feb 5, 2026
- Updated
- Feb 5, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-119, CWE-125, CWE-787, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2026CVE publishedPublication date reported by the CVE source.
- Feb 5, 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