Vulnerability in Kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd()
Summary
GSD-2021-1001659: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd(). Affects Kernel versions >= 36cf515b9bbe298e1ce7384620f0d4ec45ad3328, < 17ccc64e4fa5d3673528474bfeda814d95dc600a. 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 manages system resources and provides an interface for applications to interact with the hardware. It includes various subsystems, such as cryptography, which handle encryption and decryption operations. One of these subsystems is the Crypto Co-Processor (CCP), which offloads cryptographic operations to dedicated hardware. The ccp_run_aes_gcm_cmd() function in the CCP subsystem is responsible for executing AES-GCM encryption and decryption commands. However, this function has a vulnerability that leads to resource leaks, potentially causing memory or other resource exhaustion issues.
Vulnerability Detail
The vulnerability in ccp_run_aes_gcm_cmd() allows for resource leaks, which can result in memory or other resource exhaustion. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition by repeatedly triggering the resource leaks, leading to system instability or crashes. The vulnerability was introduced in version v4.12 of the Linux Kernel and was fixed in version v5.10.71. The fix involves commit 17ccc64e4fa5d3673528474bfeda814d95dc600a.
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. However, users can mitigate the risk by ensuring they have the latest security updates installed and following best practices for system hardening.
Conclusion
The vulnerability in the Kernel's ccp_run_aes_gcm_cmd() function can lead to resource leaks, potentially causing memory or other resource exhaustion issues. It is crucial to update the Linux Kernel to version v5.10.71 or later to mitigate the risk. Users can also use tools like Vulert to check if their system is affected by this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource leaks, potentially causing memory or other resource exhaustion issues. This can result in system instability, crashes, or denial-of-service (DoS) conditions.
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.
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 the risk.
The vulnerability itself does not provide remote code execution capabilities. However, if an attacker already has access to the system, they could potentially exploit this vulnerability to cause a denial-of-service condition.
To exploit this vulnerability, an attacker would need to have access to a system running a vulnerable version of the Linux Kernel and the ability to trigger the resource leaks in the ccp_run_aes_gcm_cmd() function.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
