Local privilege escalation via memory-map corruption
Published Nov 17, 2022 · Updated Apr 30, 2025
Improper input validation in Google Titan M on Android kernel builds allows local users with System privileges to escalate privilege. The undisclosed mprot_unmap locus accepts insufficiently validated input and can corrupt the memory mapping; Google has not published the affected code path. Exploitation requires existing System execution privileges on a supported Pixel device and no user interaction, while the resulting elevated privilege boundary remains unspecified.
Summary
What happened
Improper input validation in Google Titan M on Android kernel builds allows local users with System privileges to escalate privilege. The undisclosed mprot_unmap locus accepts insufficiently validated input and can corrupt the memory mapping; Google has not published the affected code path. Exploitation requires existing System execution privileges on a supported Pixel device and no user interaction, while the resulting elevated privilege boundary remains unspecified.
The record
- CVE
- CVE-2022-20460
- Published
- Nov 17, 2022
- Updated
- Apr 30, 2025
- Vendor
- Product
- Titan M
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 30, 2025Record 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?
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.
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