Local privilege escalation via ion_ioctl use after free
Published Apr 12, 2022 · Updated Aug 4, 2024
Use-after-free in ion_ioctl of Google Cloud Android kernel allows local users to gain privileges through crafted ION ioctl calls. The function releases or reuses ION buffer state under improper locking, permitting a concurrent operation to access freed kernel memory. Exploitation requires a local application with low privileges and no user interaction; successful exploitation can compromise kernel confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in ion_ioctl of Google Cloud Android kernel allows local users to gain privileges through crafted ION ioctl calls. The function releases or reuses ION buffer state under improper locking, permitting a concurrent operation to access freed kernel memory. Exploitation requires a local application with low privileges and no user interaction; successful exploitation can compromise kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2021-39801
- Published
- Apr 12, 2022
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-667, CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 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.
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