Refcount Leak in drm/amd/amdgpu Package
Summary
GSD-2021-1000649: drm/amd/amdgpu: fix refcount leak. Affects Kernel versions < 599e5d61ace952b0bb9bd942b198bbd0cfded1d7. 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 package is a component of the Linux Kernel that provides support for AMD GPUs. It is responsible for managing the graphics hardware and enabling communication between the GPU and the operating system. The package includes various drivers and modules that facilitate the utilization of AMD GPUs for display and computation purposes. However, a vulnerability has been identified in the package that can lead to a refcount leak.
Vulnerability Detail
The refcount leak vulnerability in the drm/amd/amdgpu package allows for the improper handling of reference counts, leading to a resource leak. When certain operations are performed, such as allocating or freeing resources, the package fails to properly increment or decrement the reference count. This can result in a situation where resources are not released when they should be, leading to memory leaks and potential resource exhaustion. An attacker could potentially exploit this vulnerability to exhaust system resources, causing denial of service or other adverse effects.
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 known workaround for this vulnerability. It is recommended to apply the patch provided by the Linux Kernel developers.
Conclusion
The refcount leak vulnerability in the drm/amd/amdgpu package of the Linux Kernel can lead to resource leaks and potential resource exhaustion. It is crucial to update the Linux Kernel to version v4.19.193 or later to mitigate this vulnerability. No known workarounds exist, and it is recommended to apply the provided patch. For additional support, contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to resource leaks and potential resource exhaustion. It could be exploited by an attacker to cause denial of service or other adverse effects.
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 the playground will provide real-time alerts for open-source vulnerabilities.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the patch to mitigate the risk.
This vulnerability requires local access to the system in order to exploit it. Remote exploitation is not possible.
For further support on vulnerability remediation, you can contact info@devnack.com. They can provide assistance and guidance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
