Local memory disclosure via unchecked ramdump creation
Published Jun 15, 2022 · Updated Aug 3, 2024
Information disclosure in the Android kernel on Google Pixel devices allows local users with System privileges to read non-secure memory. The handle_ramdump function in pixel_loader.c creates a ramdump of non-secure memory without checking whether the caller has permission. Exploitation requires local System execution privileges and no user interaction, and it exposes memory contents without reported write or service impact.
Summary
What happened
Information disclosure in the Android kernel on Google Pixel devices allows local users with System privileges to read non-secure memory. The handle_ramdump function in pixel_loader.c creates a ramdump of non-secure memory without checking whether the caller has permission. Exploitation requires local System execution privileges and no user interaction, and it exposes memory contents without reported write or service impact.
The record
- CVE
- CVE-2022-20182
- Published
- Jun 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-862, T1533
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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