Local information disclosure via VPU race
Published Mar 10, 2026 · Updated Mar 10, 2026
Information disclosure in the VPU component of Google Android kernel allows local users to read freed memory through a race condition. A VPU race leaves memory reachable after it is freed, and a subsequent read returns stale contents from the freed allocation. Exploitation requires local access, needs no additional execution privileges or user interaction, and is limited to information disclosure.
Summary
What happened
Information disclosure in the VPU component of Google Android kernel allows local users to read freed memory through a race condition. A VPU race leaves memory reachable after it is freed, and a subsequent read returns stale contents from the freed allocation. Exploitation requires local access, needs no additional execution privileges or user interaction, and is limited to information disclosure.
The record
- CVE
- CVE-2026-0121
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-416, CWE-362, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 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