Off by one vulnerability in drm/amdgpu package
Summary
GSD-2022-1002616: drm/amdgpu: Off by one in dm_dmub_outbox1_low_irq(). Affects Kernel versions >= e27c41d5b0681c597ac1894f4e02cf626e062250, < 607c5cd1a08e196d9f2bd3b25a8083ed27ad7ceb. 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 ecosystem. It provides support for AMD GPUs and handles various graphics-related functionalities. The package is responsible for managing the communication between the display manager and the AMD GPU hardware. It is widely used in Linux-based systems that utilize AMD graphics cards.
Vulnerability Detail
The vulnerability, identified as GSD-2022-1002616, exists in the dm_dmub_outbox1_low_irq() function within the drm/amdgpu package. This vulnerability is an off-by-one error, which occurs when the function fails to correctly handle a specific input, leading to a buffer overflow. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service (DoS) condition. 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 provided for this vulnerability.
Conclusion
In conclusion, the drm/amdgpu package in the Linux Kernel is affected by an off-by-one vulnerability in the dm_dmub_outbox1_low_irq() function. This vulnerability can potentially allow an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition. Users are strongly advised to update their Linux Kernel to version v5.18.4 or later to mitigate the risk associated with this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially allow an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition.
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 important to apply the recommended fix to mitigate any potential risks.
The details regarding the remote exploitability of this vulnerability have not been provided. However, it is always advisable to apply security patches promptly to minimize the risk of remote exploitation.
The recommended solution is to update the Linux Kernel to version v5.18.4 or later. It is not advisable to rely on alternative solutions or workarounds, as they may not provide comprehensive protection against the vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
