Vulnerability in drm/amdgpu Package: Off-by-One Error in amdgpu_gfx_kiq_acquire()
Summary
GSD-2022-1001375: drm/amdgpu: fix off by one in amdgpu_gfx_kiq_acquire(). Affects Kernel versions >= 71c37505e7eaa01fa259debad1a71a7ae061039d, < 946c33fefcb9dd0c2c820ef9c3fe91a45401d321. 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 to enable graphics acceleration and other GPU-related functionalities on Linux systems. The amdgpu_gfx_kiq_acquire() function is responsible for acquiring the Kernel Interface Queue (KIQ) for the AMD GPU. This queue is used for communication between the GPU and the driver. However, a vulnerability has been discovered in this function, leading to an off-by-one error.
Vulnerability Detail
The off-by-one error in amdgpu_gfx_kiq_acquire() allows an attacker to overwrite adjacent memory locations, potentially leading to memory corruption or arbitrary code execution. By exploiting this vulnerability, an attacker could gain elevated privileges or crash the system. The vulnerability was introduced in version v4.13 of the Linux Kernel and has been fixed in version v5.16.20.
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
As this vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. It is strongly advised to update to the fixed version as soon as possible.
Conclusion
In conclusion, the drm/amdgpu package in the Linux Kernel is vulnerable to an off-by-one error in the amdgpu_gfx_kiq_acquire() function. This vulnerability can be mitigated by updating the Linux Kernel to version v5.16.20 or later. It is recommended to apply the fix as soon as possible to prevent potential memory corruption or arbitrary code execution. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability allows an attacker to overwrite adjacent memory locations, potentially leading to memory corruption or arbitrary code execution. This could result in privilege escalation or system crashes.
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 known vulnerabilities, including this one.
Yes, this vulnerability can be exploited remotely if the attacker has the necessary access to the targeted system.
There are no known instances of this vulnerability being exploited in the wild at the time of this report.
For more details about this vulnerability, you can refer to the source information provided by the Cloud Security Alliance's GSD Database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001375.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.