Vulnerability in Kernel: crypto: cryptd - Protect per-CPU resource by disabling BH
Summary
GSD-2022-1002710: crypto: cryptd - Protect per-CPU resource by disabling BH. Affects Kernel versions >= 254eff771441f4ee7aa9cf770a6e4820492c9dab, < 340f65c4d8246dc3c6676f85b2bdebc797ca56c0. 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 functionalities 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 provides cryptographic services and algorithms for various security-related operations. One of the components in the crypto subsystem is cryptd, which is responsible for offloading cryptographic operations to dedicated hardware or software accelerators. However, a vulnerability has been discovered in the cryptd component that could potentially lead to security breaches and compromise the confidentiality and integrity of cryptographic operations.
Vulnerability Detail
The vulnerability in cryptd arises from a lack of proper protection for per-CPU resources. By disabling the bottom half (BH) mechanism, which handles deferred work in the Kernel, an attacker could gain unauthorized access to these resources and manipulate them to perform malicious actions. This could result in the compromise of cryptographic keys, unauthorized decryption or encryption of data, and other security breaches. The impact and attack plausibility of this vulnerability have not been proven yet, but it is crucial to address it to ensure the overall 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
As a workaround, users can disable the use of cryptd if it is not essential for their system. This can be achieved by modifying the Kernel configuration to exclude the cryptd module during the build process. However, this workaround should only be considered if the functionality provided by cryptd is not required, as it may impact the performance or compatibility of certain cryptographic operations.
Conclusion
The vulnerability in cryptd within the Kernel poses a potential risk to the security of cryptographic operations. It is crucial to update the Kernel to the latest version and ensure the proper protection of per-CPU resources. Applying the recommended fix and considering the provided workaround can help mitigate the risk of unauthorized access and manipulation. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could potentially lead to the compromise of cryptographic keys, unauthorized decryption or encryption of data, and other security breaches.
You can use tools like Vulert (https://vulert.com) 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.
As of now, there is no known exploit for this vulnerability. However, it is important to address it promptly to mitigate any potential risks.
Applying the recommended workaround of disabling the use of cryptd can provide temporary protection if the functionality is not required. However, it is still advisable to update the Kernel to the latest version as soon as possible.
You can refer to the Linux Kernel repository on Git for more information about the fix and the vulnerability. The fix was implemented in commit 340f65c4d8246dc3c6676f85b2bdebc797ca56c0, and the vulnerability was introduced in version v2.6.30 by commit 254eff771441f4ee7aa9cf770a6e4820492c9dab.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
