Refcount Leak of a dma_fence obj in drm/amd/amdgpu/amdgpu_cs
Summary
GSD-2022-1001084: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj. Affects Kernel versions < bc2d5c0775c839e2b072884f4ee6a93ba410f107. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The drm/amd/amdgpu/amdgpu_cs package is a component of the Linux Kernel that provides support for AMD GPUs. It includes functionality for managing command submission and synchronization between the CPU and GPU. This vulnerability in the package involves a refcount leak of a dma_fence object, which can lead to resource exhaustion and potential denial of service attacks.
Vulnerability Detail
The vulnerability arises from a refcount leak of a dma_fence object in the drm/amd/amdgpu/amdgpu_cs package. A dma_fence object is used for synchronization between different parts of the GPU driver. The refcount leak occurs when the object is not properly released after use, leading to a gradual accumulation of unreleased objects. This can result in resource exhaustion, potentially causing the system to become unresponsive or crash. An attacker may be able to exploit this vulnerability to launch denial of service attacks.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround available for this vulnerability. The recommended solution is to update the Linux Kernel to the fixed version.
Conclusion
In conclusion, the drm/amd/amdgpu/amdgpu_cs package in the Linux Kernel is vulnerable to a refcount leak of a dma_fence object. This can lead to resource exhaustion and potential denial of service attacks. Users should update their Linux Kernel to version v5.17.3 or later to fix the vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and potential denial of service attacks. It may cause the system to become unresponsive or crash.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for any open-source vulnerabilities, including this one.
There is no known exploit for this vulnerability at the moment. However, it is recommended to update the Linux Kernel to the fixed version to mitigate any potential risks.
The recommended solution is to update the Linux Kernel to the fixed version. There are no known alternative solutions for this specific vulnerability.
You can find more information about this vulnerability in the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and the vulnerability database maintained by the Cloud Security Alliance (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
