Local privilege escalation via improper driver locking
Published Jun 21, 2021 · Updated Aug 3, 2024
Memory corruption in Android SoC memory management drivers allows local users to elevate privileges without user interaction. The driver improperly locks shared memory-management state, allowing concurrent operations to corrupt memory; the affected function and lock remain undisclosed. Exploitation requires locally executing code but no additional execution privileges, and the published consequence is privilege escalation.
Summary
What happened
Memory corruption in Android SoC memory management drivers allows local users to elevate privileges without user interaction. The driver improperly locks shared memory-management state, allowing concurrent operations to corrupt memory; the affected function and lock remain undisclosed. Exploitation requires locally executing code but no additional execution privileges, and the published consequence is privilege escalation.
The record
- CVE
- CVE-2021-0529
- Published
- Jun 21, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-667, CAPEC-26, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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