Vulnerability in Kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd()
Summary
GSD-2021-1001566: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd(). Affects Kernel versions >= 36cf515b9bbe298e1ce7384620f0d4ec45ad3328, < 710be7c42d2f724869e5b18b21998ceddaffc4a9. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a critical component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It is responsible for managing system resources, including memory, processes, and device drivers. The crypto subsystem within the Kernel handles cryptographic operations, such as encryption and decryption. One of the components in the crypto subsystem is the ccp (Cryptographic Coprocessor) module, which offloads certain cryptographic tasks to dedicated hardware. The ccp_run_aes_gcm_cmd() function within the ccp module is responsible for executing AES-GCM (Advanced Encryption Standard - Galois/Counter Mode) commands. However, this function contains a resource leak vulnerability that can lead to potential security issues.
Vulnerability Detail
The vulnerability in ccp_run_aes_gcm_cmd() within the Kernel's crypto subsystem allows for resource leaks. Resource leaks occur when system resources, such as memory or file descriptors, are not properly released after use. In this case, the function fails to release resources under certain conditions, potentially leading to memory leaks or file descriptor leaks. Exploiting this vulnerability could result in resource exhaustion, denial of service, or even privilege escalation attacks. The impact and attack plausibility of this vulnerability have not been proven yet.
How To Fix
No fixed version is published for this vulnerability.
The vulnerability has been fixed in Linux Kernel version v4.19.209 by commit 710be7c42d2f724869e5b18b21998ceddaffc4a9. To fix the vulnerability, users should update their Kernel to version v4.19.209 or later. It is recommended to regularly update the Kernel to ensure the latest security patches are applied.
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. However, users can mitigate the risk by updating their Kernel to the fixed version as mentioned in the 'how_to_fix' section.
Conclusion
The vulnerability in the Kernel's crypto subsystem, specifically in the ccp_run_aes_gcm_cmd() function, allows for resource leaks. It is crucial to update the Kernel to version v4.19.209 or later to fix this vulnerability and ensure the system is protected against potential attacks. Regularly updating the Kernel is recommended to stay up to date with the latest security patches. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could include resource exhaustion, denial of service, or privilege escalation attacks. However, the actual impact and attack plausibility have not been proven yet.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
The specific prerequisites for exploiting this vulnerability have not been mentioned in the provided information. However, it is always recommended to keep systems up to date with the latest security patches to minimize the risk of exploitation.
For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide assistance and guidance in addressing the vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.