Local privilege escalation via Binder credential race
Published Mar 16, 2022 · Updated Aug 4, 2024
Race condition in the Linux Kernel Android Binder driver allows local users to escalate privileges through incorrect SELinux security checks. binder.c passes a binder_proc task_struct to SELinux, whose later task-to-SID conversion can race with credential changes and select the wrong security context. Exploitation requires local code execution and a kernel built with the Binder driver, but no user interaction or additional execution privileges.
Summary
What happened
Race condition in the Linux Kernel Android Binder driver allows local users to escalate privileges through incorrect SELinux security checks. binder.c passes a binder_proc task_struct to SELinux, whose later task-to-SID conversion can race with credential changes and select the wrong security context. Exploitation requires local code execution and a kernel built with the Binder driver, but no user interaction or additional execution privileges.
The record
- CVE
- CVE-2021-39686
- Published
- Mar 16, 2022
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- Unavailable
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?
Published CVSS scores
No CVSS assessment is available in this record.
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