Vulnerability in Kernel: drm/amdgpu/psp
Summary
GSD-2022-1002813: drm/amdgpu/psp: move PSP memory alloc from hw_init to sw_init. Affects Kernel versions < 648befb200242cd0eaa41129544c675644ecc41d. 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 is a fundamental component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. The drm/amdgpu/psp module within the Kernel is specifically designed for AMD GPUs and handles various tasks related to power management and security. This vulnerability in the drm/amdgpu/psp module involves a memory allocation issue that has been identified and addressed.
Vulnerability Detail
The vulnerability in the drm/amdgpu/psp module involves the improper allocation of PSP (Platform Security Processor) memory. In the original implementation, the memory allocation was performed during the hardware initialization phase (hw_init). However, this approach posed a potential security risk. To mitigate this, the memory allocation has been moved to the software initialization phase (sw_init) in the fixed version of the Linux Kernel. The vulnerability could potentially be exploited by an attacker to gain unauthorized access or execute arbitrary code on a system with an affected version of the Kernel.
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 →
Conclusion
In conclusion, the vulnerability in the drm/amdgpu/psp module of the Kernel has been addressed in the fixed version v5.18.3. Users are advised to update their Linux Kernel to this version or later to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could potentially allow an attacker to gain unauthorized access or execute arbitrary code on a system with an affected version of the Kernel.
No, the recommended solution is to update the Linux Kernel to the fixed version.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time monitoring and alerts for open-source vulnerabilities, including this one.
No, the vulnerability is fixed in Linux Kernel version v5.18.3 and later. Versions prior to this are affected.
You can refer to the vulnerability details in the GSD database at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002813.json for more information.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
