Refcount Leak of dma_fence obj in drm/amd/amdgpu/amdgpu_cs
Summary
GSD-2022-1002016: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj. Affects Kernel versions < 927beb05aaa429c883cc0ec6adc48964b187e291. 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 the amdgpu_cs module, which is responsible for handling command submission and management for AMD GPUs. 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 amdgpu_cs module. A dma_fence object is used to synchronize GPU operations with other parts of the system. The refcount leak occurs when the object is not properly released after use, leading to a gradual accumulation of unreleased objects. An attacker can exploit this vulnerability by repeatedly triggering the creation of dma_fence objects, eventually exhausting system resources and causing a denial of service. The impact of this vulnerability can vary depending on the system's workload and available resources.
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 mentioned for this vulnerability. The recommended approach is to apply the fix by updating the Linux Kernel to the patched version.
Conclusion
In conclusion, the vulnerability in the drm/amd/amdgpu/amdgpu_cs package involves a refcount leak of a dma_fence object. This can lead to resource exhaustion and potential denial of service attacks. To mitigate this vulnerability, it is recommended to update the Linux Kernel to version v5.10.111 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the system's workload and available resources. It can lead to resource exhaustion and potential denial of service attacks.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate the risk.
This vulnerability can be exploited on systems running the affected version of the Linux Kernel with the drm/amd/amdgpu/amdgpu_cs module enabled.
The recommended approach to mitigate this vulnerability is to update the Linux Kernel to the patched version. There are no known alternative mitigations or workarounds mentioned for this specific vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
