Vulnerability in drm/amdgpu Package: Init GFX10_ADDR_CONFIG for VCN v3 in DPG mode
Summary
GSD-2021-1000301: drm/amdgpu: Init GFX10_ADDR_CONFIG for VCN v3 in DPG mode. Affects Kernel versions >= 99541f392b4d0584594a2492582b3f262a8f2643, < c9864a6b0ab3860e9f462b5f23b653762c1657a9. 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. This vulnerability specifically affects the package's handling of GFX10_ADDR_CONFIG initialization for VCN v3 in DPG mode.
Vulnerability Detail
The vulnerability arises from a missing initialization of GFX10_ADDR_CONFIG for VCN v3 in DPG mode in the drm/amdgpu package. While the impact and attack plausibility have not been proven, this vulnerability has the potential to lead to security issues. It was introduced in Linux Kernel version v5.9 by commit 99541f392b4d0584594a2492582b3f262a8f2643 and has been fixed in version v5.12.4 by commit c9864a6b0ab3860e9f462b5f23b653762c1657a9.
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 mentioned for this vulnerability.
Conclusion
In conclusion, the drm/amdgpu package in the Linux Kernel is vulnerable to an issue related to the initialization of GFX10_ADDR_CONFIG for VCN v3 in DPG mode. It is recommended to update the Linux Kernel to version v5.12.4 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 impact of this vulnerability is currently unknown as the actual attack plausibility has not been proven. However, it has the potential to lead to security issues.
This vulnerability was introduced in Linux Kernel version v5.9 and affects all versions up to v5.12.3.
Yes, this vulnerability has been fixed in Linux Kernel version v5.12.4 by commit c9864a6b0ab3860e9f462b5f23b653762c1657a9.
You can find more information about this vulnerability in the official Linux Kernel repository and the vulnerability database maintained by the Cloud Security Alliance.
To update the Linux Kernel, you can pull the latest changes from the official Linux Kernel repository using the provided link.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
