Vulnerability in drm/amdgpu Package: gart.bo pin_count Leak
Summary
GSD-2021-1001679: drm/amdgpu: fix gart.bo pin_count leak. Affects Kernel versions < 18d1c5ea3798ba42cfa0f8b2264d873463facb03. 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/amdgpu package is a component of the Linux Kernel that provides support for AMD GPUs. It includes drivers and modules necessary for the proper functioning of AMD graphics cards on Linux systems. The package is responsible for managing memory allocation, command submission, and other GPU-related operations. However, a vulnerability has been discovered in the package that could lead to a gart.bo pin_count leak.
Vulnerability Detail
The gart.bo pin_count leak vulnerability in the drm/amdgpu package allows an attacker to cause a memory leak by manipulating the pin_count of a gart.bo object. By repeatedly incrementing the pin_count without decrementing it, an attacker can exhaust the available memory resources, leading to a denial-of-service condition. This vulnerability could potentially be exploited to crash the system or cause instability. It is important to note that 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
There is no known workaround for this vulnerability. It is essential to update the Linux Kernel to the fixed version to mitigate the risk.
Conclusion
The gart.bo pin_count leak vulnerability in the drm/amdgpu package can be mitigated by updating the Linux Kernel to version v5.14.13 or later. It is crucial to keep systems up to date with the latest security patches to ensure the stability and security of the system. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from system crashes to instability. However, the exact impact and attack plausibility have not been proven.
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 provide real-time alerts for open-source vulnerabilities.
No, there is no known workaround for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.
The remote exploitability of this vulnerability has not been determined. However, it is always recommended to keep systems up to date with the latest security patches.
You can find more information about this vulnerability in the GSD-2021-1001679.json file available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/GSD-2021-1001679.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
