Local privilege escalation via improper DRAM address validation
Published Dec 16, 2022 · Updated Apr 18, 2025
Improper input validation in Google Pixel LDFW drm_access_control.c allows local users to escalate privileges in the Android kernel. The valid_out_of_special_sec_dram_addr function does not correctly reject an invalid value during special secure DRAM address checks; Google has not disclosed the rejected condition or resulting privileged operation. Exploitation requires local low-privileged access, needs no user interaction, and grants elevated privileges within the affected Pixel firmware.
Summary
What happened
Improper input validation in Google Pixel LDFW drm_access_control.c allows local users to escalate privileges in the Android kernel. The valid_out_of_special_sec_dram_addr function does not correctly reject an invalid value during special secure DRAM address checks; Google has not disclosed the rejected condition or resulting privileged operation. Exploitation requires local low-privileged access, needs no user interaction, and grants elevated privileges within the affected Pixel firmware.
The record
- CVE
- CVE-2022-20586
- Published
- Dec 16, 2022
- Updated
- Apr 18, 2025
- Vendor
- Product
- Pixel LDFW
- Classifications
- CWE-20, T1404
- Attack vector
- local
- Privileges
- authenticated
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