Local information disclosure via improper address validation
Published Dec 16, 2022 · Updated Apr 18, 2025
Information disclosure in Android kernel LDFW allows local users with System privileges to read protected data without user interaction. The valid_va_secbuf_check function in drm_access_control.c inadequately validates its input before accepting a secure-buffer address. The flaw is Pixel-specific, requires System execution privileges, and affects confidentiality only; Google has not published further input details.
Summary
What happened
Information disclosure in Android kernel LDFW allows local users with System privileges to read protected data without user interaction. The valid_va_secbuf_check function in drm_access_control.c inadequately validates its input before accepting a secure-buffer address. The flaw is Pixel-specific, requires System execution privileges, and affects confidentiality only; Google has not published further input details.
The record
- CVE
- CVE-2022-20589
- Published
- Dec 16, 2022
- Updated
- Apr 18, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-20
- 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?
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.
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