Kernel privilege escalation via premature reference resurrection
Published Jun 15, 2022 · Updated Aug 3, 2024
Use-after-free in the Android kernel allows local users with System execution privileges to escalate privileges without user interaction. A failed io_uring registration path resurrects context references before release completion, allowing callback teardown to reach freed memory in rcu_cblist_dequeue. Exploitation requires local access and existing System execution privileges; successful abuse grants kernel-level privileges.
Summary
What happened
Use-after-free in the Android kernel allows local users with System execution privileges to escalate privileges without user interaction. A failed io_uring registration path resurrects context references before release completion, allowing callback teardown to reach freed memory in rcu_cblist_dequeue. Exploitation requires local access and existing System execution privileges; successful abuse grants kernel-level privileges.
The record
- CVE
- CVE-2022-20153
- Published
- Jun 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-667, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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