Local privilege escalation via DMA-BUF release race
Published Apr 12, 2022 · Updated Aug 3, 2024
Use-after-free in Android kernel DMA-BUF code allows local users to escalate privileges by racing buffer closure with debug-info reads. dma_buf_release removes a buffer from db_list only after __fput frees file->f_inode, allowing dma_buf_debug_show to read the freed inode during the gap. Exploitation requires local low-privileged execution and control of the close/read race, but no user interaction or additional privileges.
Summary
What happened
Use-after-free in Android kernel DMA-BUF code allows local users to escalate privileges by racing buffer closure with debug-info reads. dma_buf_release removes a buffer from db_list only after __fput frees file->f_inode, allowing dma_buf_debug_show to read the freed inode during the gap. Exploitation requires local low-privileged execution and control of the close/read race, but no user interaction or additional privileges.
The record
- CVE
- CVE-2021-0707
- Published
- Apr 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 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