Vulnerability in drm/amdgpu package: off by one in amdgpu_gfx_kiq_acquire()
Summary
GSD-2022-1002403: drm/amdgpu: fix off by one in amdgpu_gfx_kiq_acquire(). Affects Kernel versions >= 71c37505e7eaa01fa259debad1a71a7ae061039d, < dd3a74d9e1b7ce143f0aec04da8691a764392f67. 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 graphics-related functionality. The amdgpu_gfx_kiq_acquire() function is responsible for acquiring the Kernel Interface Queue (KIQ) for the graphics engine. This vulnerability arises from an off-by-one error in the implementation of this function.
Vulnerability Detail
The off-by-one error in amdgpu_gfx_kiq_acquire() can lead to a buffer overflow, potentially allowing an attacker to overwrite adjacent memory. Exploiting this vulnerability could result in arbitrary code execution or privilege escalation. The issue was introduced in version v4.13 of the Linux Kernel and has been addressed in version v4.14.276 by commit dd3a74d9e1b7ce143f0aec04da8691a764392f67.
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
The off-by-one error in amdgpu_gfx_kiq_acquire() within the drm/amdgpu package of the Linux Kernel can potentially lead to arbitrary code execution or privilege escalation. It is crucial to update the Linux Kernel to version v4.14.276 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to arbitrary code execution or privilege escalation.
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 it will provide real-time alerts for open-source vulnerabilities.
At the time of this report, no known exploits have been identified for this vulnerability.
For more details about this vulnerability, you can refer to the source information provided by the Cloud Security Alliance: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002403.json
If updating the Linux Kernel is not feasible, it is recommended to consult with the Linux Kernel community or seek professional assistance to explore alternative mitigation strategies.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.