Out-of-Bound Writes in drm/amdgpu Package
Summary
UVI-2021-1002128: drm/amdgpu: Fix even more out of bound writes from debugfs. Affects Kernel versions >= 918698d5c2b50433714d2042f55b55b090faa167, < 9eb4bdd554fc31a5ef6bf645a20ff21618ce45a9. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The drm/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 graphics rendering on AMD GPUs. The package includes various drivers and modules that interact with the GPU hardware and provide an interface for user-space applications to utilize the GPU's capabilities.
Vulnerability Detail
The vulnerability identified as UVI-2021-1002128 in the drm/amdgpu package involves out-of-bound writes from debugfs. This vulnerability allows an attacker to write data beyond the intended boundaries of a buffer, potentially leading to memory corruption and arbitrary code execution. The issue was introduced in version v5.10 of the Linux Kernel and was fixed in version v5.14.16. 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
No specific workaround has been mentioned for this vulnerability.
Conclusion
The out-of-bound writes vulnerability in the drm/amdgpu package can potentially lead to memory corruption and arbitrary code execution. It is crucial to update the Linux Kernel to version v5.14.16 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 could potentially be memory corruption and arbitrary code execution. However, the actual impact and attack plausibility have not been proven yet.
You can use the Vulert Playground (https://vulert.com/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.
As of now, there is no known exploit for this vulnerability. However, it is always recommended to apply security patches and updates to mitigate any potential risks.
The primary solution to fix this vulnerability is to update the Linux Kernel to the latest version. However, if updating the kernel is not feasible or practical, it is recommended to consult with security experts or the package maintainers for alternative mitigation strategies.
You can find more information about this vulnerability, including the specific commits that fixed it, in the vulnerability database maintained by the Cloud Security Alliance. The source link is provided in the database_specific field of the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
