S-EL1 privilege escalation via LDFW buffer overwrite
Published Dec 16, 2022 · Updated Apr 18, 2025
Out-of-bounds write in Android kernel LDFW allows local users with System privileges to escalate into S-EL1 without interaction. The ppmp_unprotect_mfcfw_buf function in drm_fw.c inadequately validates input before writing beyond its intended buffer boundary. Exploitation requires existing System execution privileges on a supported Pixel device and raises code execution into the secure S-EL1 firmware context.
Summary
What happened
Out-of-bounds write in Android kernel LDFW allows local users with System privileges to escalate into S-EL1 without interaction. The ppmp_unprotect_mfcfw_buf function in drm_fw.c inadequately validates input before writing beyond its intended buffer boundary. Exploitation requires existing System execution privileges on a supported Pixel device and raises code execution into the secure S-EL1 firmware context.
The record
- CVE
- CVE-2022-20583
- Published
- Dec 16, 2022
- Updated
- Apr 18, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1068
- 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.
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