Local privilege escalation via delete_protocol use after free
Published Jan 14, 2022 · Updated Aug 4, 2024
Elevation of privilege in Android kernel allows local users to execute arbitrary code through a use-after-free in delete_protocol. The delete_protocol function in main.c uses memory after it has been freed, enabling arbitrary kernel code execution and privilege escalation. Exploitation requires a locally running application on an affected Android device and no user interaction; the resulting impact is bounded to elevated privileges on the device.
Summary
What happened
Elevation of privilege in Android kernel allows local users to execute arbitrary code through a use-after-free in delete_protocol. The delete_protocol function in main.c uses memory after it has been freed, enabling arbitrary kernel code execution and privilege escalation. Exploitation requires a locally running application on an affected Android device and no user interaction; the resulting impact is bounded to elevated privileges on the device.
The record
- CVE
- CVE-2021-39681
- Published
- Jan 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 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.
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