Out of Bounds Write Vulnerability in drm/amdgpu Package
Summary
GSD-2021-1002200: drm/amdgpu: fix out of bounds write. Affects Kernel versions < 5afa7898ab7a0ec9c28556a91df714bf3c2f725e. 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 is responsible for managing graphics and display functionality on systems using AMD graphics cards. The package is widely used in Linux distributions and is critical for proper GPU operation. However, a vulnerability has been discovered in the package that allows for an out of bounds write.
Vulnerability Detail
The out of bounds write vulnerability in the drm/amdgpu package allows an attacker to write data beyond the boundaries of an allocated buffer. This can lead to memory corruption, which may result in various security issues, including remote code execution or privilege escalation. The vulnerability originates from a flaw in the package's code, which fails to properly validate input data, allowing an attacker to manipulate memory addresses and write arbitrary data. The impact of this vulnerability can be severe, potentially compromising the security and stability of affected systems.
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 apply the official patch by updating the Linux Kernel to the fixed version.
Conclusion
The out of bounds write vulnerability in the drm/amdgpu package poses a significant risk to systems using AMD GPUs. It is crucial to update the Linux Kernel to version v5.15 or later to ensure the vulnerability is patched. Failure to do so may result in memory corruption and potential security breaches. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory corruption, which may result in various security issues, including remote code execution or privilege escalation.
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 analyze it for any known vulnerabilities.
The vulnerability is present in versions of the Linux Kernel prior to v5.15. It is recommended to update to the latest available kernel version to ensure the vulnerability is patched.
At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the patch as soon as possible to mitigate any potential risks.
The vulnerability was discovered by an automated security analysis tool and reported to the Linux Kernel security team.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
