Vulnerability in drm/amdgpu Package: gart.bo pin_count Leak
Summary
UVI-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 the Direct Rendering Manager (DRM) driver for AMD graphics cards. The package is responsible for managing memory, rendering, and other GPU-related operations. The vulnerability in question involves a pin_count leak in the gart.bo component of the package.
Vulnerability Detail
The vulnerability in the drm/amdgpu package allows for a pin_count leak in the gart.bo component. This leak can lead to memory corruption and potentially be exploited by an attacker to gain unauthorized access or execute arbitrary code. The issue has been identified and fixed in Linux Kernel version v5.14.13 by commit 18d1c5ea3798ba42cfa0f8b2264d873463facb03.
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 vulnerability in the drm/amdgpu package has been identified and fixed in Linux Kernel version v5.14.13. It is crucial to update the Linux Kernel to the fixed version to mitigate the risk of memory corruption and potential unauthorized access. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory corruption and potentially be exploited by attackers to gain unauthorized access or execute arbitrary code.
No, there is no known workaround. Updating the Linux Kernel to the fixed version is the recommended solution.
The vulnerability is present in versions prior to v5.14.13 of the Linux Kernel.
The vulnerability was discovered through code analysis and testing.
There are no known exploits for this vulnerability at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
