Local privilege escalation via out-of-bounds write
Published Nov 17, 2022 · Updated Apr 30, 2025
Out-of-bounds write in Google Titan M firmware allows local users with System execution privileges to escalate privileges. An undisclosed Titan M firmware operation writes beyond a buffer because it omits a bounds check; Google has not published the function or input. Exploitation requires existing System execution privileges on a Pixel device, needs no user interaction, and raises privileges locally.
Summary
What happened
Out-of-bounds write in Google Titan M firmware allows local users with System execution privileges to escalate privileges. An undisclosed Titan M firmware operation writes beyond a buffer because it omits a bounds check; Google has not published the function or input. Exploitation requires existing System execution privileges on a Pixel device, needs no user interaction, and raises privileges locally.
The record
- CVE
- CVE-2022-20428
- 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?
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.
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