CVE-2021-0707: Use-after-free in dmabuffs_dname

:linux_kernel: Updated 02 Oct 2025

Summary

01/04/2022
Yes i
High
Not published

CVE-2021-0707: In dma_buf_release of dma-buf.c, there is a possible memory corruption due to a use after free. Affects :linux_kernel: versions >= :0, < :2022-04-05. Fixed in :2022-04-05. How to fix ↓

Also tracked for

The same CVE-2021-0707 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package under scrutiny is the Linux Kernel, specifically the Android ecosystem. The Linux Kernel is the core component of the Android operating system, responsible for managing system resources and providing essential functionality. The vulnerability in question, identified as CVE-2021-0707, affects the dmabuffs_dname function in dma-buf.c. This function is responsible for releasing a DMA buffer, which is a mechanism for sharing memory between different devices or subsystems. The vulnerability arises from a use-after-free issue in the dma_buf_release function, leading to potential memory corruption. Exploitation of this vulnerability could result in local escalation of privilege, without requiring any additional execution privileges or user interaction.

Vulnerability Detail

The vulnerability, CVE-2021-0707, is a use-after-free issue in the dmabuffs_dname function of the Linux Kernel's dma-buf.c file. When a DMA buffer is released, the dma_buf_release function is called. However, due to a programming error, there is a possibility of memory corruption occurring after the buffer has been freed. This can lead to a local escalation of privilege, allowing an attacker to gain elevated privileges on the affected system. The vulnerability does not require any additional execution privileges or user interaction for exploitation.

How To Fix

Minimum fixed version

:2022-04-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to a patched version.

Conclusion

In conclusion, the CVE-2021-0707 vulnerability in the Linux Kernel's dmabuffs_dname function poses a risk of local privilege escalation. To mitigate this vulnerability, it is crucial to update the Linux Kernel to a version that includes the necessary patch. No known workarounds exist for this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for :linux_kernel: →

Share this vulnerability

FAQ

A use-after-free vulnerability occurs when a program continues to use a memory region after it has been freed. This can lead to memory corruption and potentially allow an attacker to execute arbitrary code or gain elevated privileges.

The impact of this vulnerability is a local escalation of privilege. An attacker who successfully exploits this vulnerability could gain elevated privileges on the affected system, potentially allowing them to perform unauthorized actions or access sensitive information.

No, user interaction is not required for exploitation of this vulnerability. An attacker can exploit the vulnerability without any user interaction.

The known mitigation for this vulnerability is to update the Linux Kernel to a version that includes the fix. Applying the patch will eliminate the use-after-free issue and prevent the memory corruption that can lead to privilege escalation.

More information about the fix for this vulnerability can be found in the Android Open Source Project (AOSP) repository. The fix was implemented in the Linux Kernel version released on April 5, 2022.

Related vulnerabilities

Recent vulnerabilities recorded for :linux_kernel:.

How To Fix

Minimum fixed version

:2022-04-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback