Kernel privilege escalation via sparse-memory bounds check
Published Dec 4, 2023 · Updated Aug 2, 2024
Kernel privilege escalation in Google Android SoC allows local users to gain kernel privileges through a PowerVR GPU memory operation. PMRChangeSparseMemOSMem in physmem_osmem_linux.c performs an incorrect bounds check before modifying sparse OS memory, causing an out-of-bounds write. Exploitation requires local access to an affected device with the PowerVR GPU component; no user interaction or additional execution privileges are required.
Summary
What happened
Kernel privilege escalation in Google Android SoC allows local users to gain kernel privileges through a PowerVR GPU memory operation. PMRChangeSparseMemOSMem in physmem_osmem_linux.c performs an incorrect bounds check before modifying sparse OS memory, causing an out-of-bounds write. Exploitation requires local access to an affected device with the PowerVR GPU component; no user interaction or additional execution privileges are required.
The record
- CVE
- CVE-2023-21218
- Published
- Dec 4, 2023
- Updated
- Aug 2, 2024
- Vendor
- Product
- Android
- Classifications
- T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 SoC
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