Local privilege escalation via duplicate backend cleanup
Published Jun 15, 2022 · Updated Aug 4, 2024
Double free in the Android 12L Framework allows local users to escalate privileges during servicemanager startup without user interaction. The property backend closef routine frees backend state after an initialization error, and selabel_close then invokes the same cleanup routine again. Exploitation requires a local user to trigger that initialization failure during servicemanager startup, enabling memory corruption and privilege escalation.
Summary
What happened
Double free in the Android 12L Framework allows local users to escalate privileges during servicemanager startup without user interaction. The property backend closef routine frees backend state after an initialization error, and selabel_close then invokes the same cleanup routine again. Exploitation requires a local user to trigger that initialization failure during servicemanager startup, enabling memory corruption and privilege escalation.
The record
- CVE
- CVE-2021-39806
- Published
- Jun 15, 2022
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-415, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 15, 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-12L
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.
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