Local privilege escalation via coherent-memory allocation race
Published Mar 16, 2022 · Updated Aug 4, 2024
Memory corruption in the Android kernel allows local users with System execution privileges to elevate privileges without user interaction. The gasket_alloc_coherent_memory function in gasket_page_table.c allocates coherent page-table memory without sufficient synchronization, allowing concurrent execution to corrupt memory. Exploitation requires local access and existing System execution privileges; successful exploitation raises privileges without user action.
Summary
What happened
Memory corruption in the Android kernel allows local users with System execution privileges to elevate privileges without user interaction. The gasket_alloc_coherent_memory function in gasket_page_table.c allocates coherent page-table memory without sufficient synchronization, allowing concurrent execution to corrupt memory. Exploitation requires local access and existing System execution privileges; successful exploitation raises privileges without user action.
The record
- CVE
- CVE-2021-39735
- Published
- Mar 16, 2022
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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