Fix off by one vulnerability in drm/amdgpu package
Summary
GSD-2022-1001702: drm/amdgpu: fix off by one in amdgpu_gfx_kiq_acquire(). Affects Kernel versions >= 71c37505e7eaa01fa259debad1a71a7ae061039d, < 5ba9d78a72948325ecdb4dca2a31a46bc9169574. 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 necessary drivers and modules for managing graphics and display functionality on systems with AMD graphics cards. The package is widely used in Linux distributions and is critical for proper GPU operation and performance.
Vulnerability Detail
The vulnerability in the drm/amdgpu package is an off by one error in the amdgpu_gfx_kiq_acquire() function. This error allows an attacker to overwrite adjacent memory locations, potentially leading to memory corruption, crashes, or even arbitrary code execution. The vulnerability was introduced in version v4.13 of the Linux Kernel and has been present until version v5.15.34. 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 available for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.
Conclusion
The off by one vulnerability in the drm/amdgpu package can have serious consequences, including memory corruption and potential code execution. It is crucial to update the Linux Kernel to version v5.15.34 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from memory corruption and crashes to potential arbitrary code execution. However, the actual impact and attack plausibility have not been proven yet.
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 any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is always recommended to apply security updates promptly to mitigate any potential risks.
While it is possible to manually apply a patch for this vulnerability, it is recommended to update the Linux Kernel to the fixed version instead. Manually applying patches can be complex and error-prone, and it is best to rely on official updates provided by the Linux distribution or the Kernel maintainers.
The recommended solution is to update the Linux Kernel to the fixed version. Alternative solutions may involve modifying the affected code manually, but this is not recommended due to the complexity and potential for introducing new issues. It is best to follow the official update process.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
