Vulnerability in Kernel Package: drm/amdgpu/ucode
Summary
GSD-2022-1003375: drm/amdgpu/ucode: Remove firmware load type check in amdgpu_ucode_free_bo. Affects Kernel versions < b305469ed00420e53c66064b554531d6fbd98d5b. 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 Kernel package is a crucial component of the Linux operating system, responsible for managing the system's core functionality. It provides essential services and interfaces for hardware, device drivers, and system processes. The drm/amdgpu/ucode module within the Kernel package specifically handles firmware loading for AMD GPUs. This module ensures that the correct firmware is loaded onto the GPU for proper operation.
Vulnerability Detail
The vulnerability identified in the drm/amdgpu/ucode module involves a firmware load type check in the amdgpu_ucode_free_bo function. This check is intended to ensure that the firmware being freed is of the correct type. However, this check is unnecessary and can be exploited by an attacker. By manipulating the firmware load type, an attacker could potentially cause a denial-of-service (DoS) condition or execute arbitrary code on the affected system. 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
There is no specific workaround mentioned for this vulnerability.
Conclusion
In conclusion, the vulnerability in the drm/amdgpu/ucode module of the Kernel package poses a potential risk to affected systems. It is crucial to update the Kernel package to version v5.15.46 or later to patch this vulnerability and ensure the security of the system. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from a denial-of-service (DoS) condition to the execution of arbitrary code on the affected system. However, the actual impact and attack plausibility have not been proven yet.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.
Yes, a fix for this vulnerability is available in the Linux Kernel version v5.15.46. It is recommended to update your Kernel package to this version or a later one to ensure the vulnerability is patched.
There are currently no known exploits for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
You can find more information about this vulnerability in the GSD-2022-1003375 JSON file available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1003xxx/GSD-2022-1003375.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
