Refcount Leak of dma_fence obj in drm/amd/amdgpu/amdgpu_cs
Summary
GSD-2022-1001739: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj. Affects Kernel versions < 3edd8646cb7c11b57c90e026bda6f21076223f5b. 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 handles command submission and management for the AMD GPU driver. The package is responsible for managing the execution of GPU commands and ensuring synchronization between different GPU operations.
Vulnerability Detail
The vulnerability in drm/amd/amdgpu/amdgpu_cs involves a refcount leak of a dma_fence object. A dma_fence object is used to synchronize GPU operations and ensure that dependencies between different GPU commands are met. However, due to a programming error, the refcount of a dma_fence object is not properly decremented, leading to a memory leak. This vulnerability can be exploited by an attacker to exhaust system memory and potentially cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet.
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.
Conclusion
The vulnerability in drm/amd/amdgpu/amdgpu_cs involving a refcount leak of a dma_fence object can potentially lead to a denial-of-service condition. It is recommended to update the Linux Kernel to version v5.15.34 or later to fix this vulnerability. Further analysis is required to determine the actual impact and exploitability of this vulnerability. For additional support, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, it has the potential to cause a denial-of-service condition by exhausting system memory.
You can use the Vulert Playground (https://vulert.com/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.
There are no known exploits for this vulnerability at the moment. However, it is always recommended to apply security patches and updates to mitigate potential risks.
The remote exploitability of this vulnerability has not been determined yet. Further analysis is required to assess the potential for remote exploitation.
For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
