Refcount Leak of a dma_fence obj in drm/amd/amdgpu/amdgpu_cs
Summary
GSD-2022-1002322: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj. Affects Kernel versions < 72d77ddb2224ebc00648f4f78f8a9a259dccbdf7. 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 is responsible for managing command submission and execution on the GPU. The package utilizes dma_fence objects to synchronize and track the progress of GPU commands. These objects are reference-counted to ensure proper memory management and prevent resource leaks.
Vulnerability Detail
The vulnerability in drm/amd/amdgpu/amdgpu_cs involves a refcount leak of a dma_fence object. When certain conditions are met, the package fails to properly release the reference to the dma_fence object, leading to a memory leak. This vulnerability could potentially be exploited by an attacker to exhaust system memory and cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven.
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
No workaround has been provided for this vulnerability.
Conclusion
The refcount leak vulnerability in drm/amd/amdgpu/amdgpu_cs has been addressed in Linux Kernel version v4.19.238. Users are advised to update their Kernel to the fixed version to ensure the security of their systems. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is a potential memory leak, which could lead to system instability and denial-of-service conditions.
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 vulnerabilities in real-time.
No known exploit for this vulnerability has been reported at this time.
The specific system requirements for exploiting this vulnerability have not been disclosed.
No configuration changes have been identified as a mitigation for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
