Local privilege escalation via Binder teardown race
Published Feb 13, 2020 · Updated Aug 4, 2024
Use-after-free in the Android kernel Binder driver allows local users to escalate privileges without user interaction. binder_thread_release frees a Binder thread while ep_remove_waitqueue can still access its wait queue because teardown does not wait for an RCU grace period. A local process must win the high-complexity race; successful exploitation executes code in a privileged process.
Summary
What happened
Use-after-free in the Android kernel Binder driver allows local users to escalate privileges without user interaction. binder_thread_release frees a Binder thread while ep_remove_waitqueue can still access its wait queue because teardown does not wait for an RCU grace period. A local process must win the high-complexity race; successful exploitation executes code in a privileged process.
The record
- CVE
- CVE-2020-0030
- Published
- Feb 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-362, CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 13, 2020CVE 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