Local privilege escalation via missing bounds check
Published Dec 16, 2022 · Updated Apr 18, 2025
Privilege escalation in Google Pixel Firmware for the Android kernel allows local users with System privileges to gain elevated access. The firmware handles sensitive memory without a required bounds check, permitting out-of-bounds access; Google has not disclosed a narrower function or input path. Exploitation requires local System execution privileges and no user interaction, and the published record does not identify the resulting privilege level.
Summary
What happened
Privilege escalation in Google Pixel Firmware for the Android kernel allows local users with System privileges to gain elevated access. The firmware handles sensitive memory without a required bounds check, permitting out-of-bounds access; Google has not disclosed a narrower function or input path. Exploitation requires local System execution privileges and no user interaction, and the published record does not identify the resulting privilege level.
The record
- CVE
- CVE-2022-20599
- Published
- Dec 16, 2022
- Updated
- Apr 18, 2025
- Vendor
- Product
- Google Pixel Firmware
- Classifications
- CWE-119, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 18, 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.
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