Local privilege escalation via improper input validation
Published Nov 17, 2022 · Updated Apr 30, 2025
Memory corruption in Google Titan M firmware on affected Pixel devices allows local users with System privileges to elevate privileges. Google has not disclosed the affected function or input; the public record states only that improper input validation permits memory corruption. System-level execution access is required, no user interaction is needed, and the disclosed consequence is local privilege escalation.
Summary
What happened
Memory corruption in Google Titan M firmware on affected Pixel devices allows local users with System privileges to elevate privileges. Google has not disclosed the affected function or input; the public record states only that improper input validation permits memory corruption. System-level execution access is required, no user interaction is needed, and the disclosed consequence is local privilege escalation.
The record
- CVE
- CVE-2022-20427
- 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