Vulnerability in Kernel: crypto: ccp - Ensure psp_ret is always init'd in __sev_platform_init_locked()
Summary
GSD-2022-1001280: crypto: ccp - Ensure psp_ret is always init'd in __sev_platform_init_locked(). Affects Kernel versions >= e423b9d75e779d921e6adf5ac3d0b59400d6ba7e, < 590c08b061214268a1fe3b2def65969deac075f2. 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 critical component of the Linux operating system that provides core functionality and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the overall stability and security of the system. The crypto subsystem within the Kernel is responsible for providing cryptographic services and algorithms. One specific component, ccp, is a driver for the AMD Cryptographic Coprocessor (CCP) found in certain AMD processors. The ccp driver enables hardware acceleration for cryptographic operations, improving performance and efficiency. However, a vulnerability has been identified in the ccp driver that can lead to potential security issues.
Vulnerability Detail
The vulnerability in the ccp driver specifically affects the __sev_platform_init_locked() function. In this function, the variable 'psp_ret' is not always properly initialized, which can result in uninitialized memory usage and potential security vulnerabilities. An attacker may be able to exploit this vulnerability to gain unauthorized access, execute arbitrary code, or cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven, but it is important to address it to ensure the security of the system.
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
The vulnerability in the Kernel's ccp driver can lead to potential security risks, including unauthorized access, arbitrary code execution, or denial-of-service attacks. It is crucial to update the Linux Kernel to version v5.17.2 or later to fix this vulnerability. Vulert's playground can be used to check if your system is affected, and further support on vulnerability remediation can be obtained by contacting DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it has the potential to allow unauthorized access, arbitrary code execution, or denial-of-service attacks.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.
Yes, a patch is available in the Linux Kernel version v5.17.2. It is recommended to update to this version or a later version to fix the vulnerability.
The remote exploitability of this vulnerability is not yet determined. However, it is important to apply the patch as a precautionary measure.
There are no known instances of this vulnerability being exploited at the time of this report. However, it is always recommended to apply security patches to mitigate potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
