Vulnerability in Kernel: crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd()

Kernel Updated 02 Oct 2025

Summary

19/10/2021
N/A
No i
Unrated
Not published

UVI-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 ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a critical component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the security and stability of the system. The crypto subsystem within the Kernel is responsible for cryptographic operations, including encryption and decryption. One of the components in the crypto subsystem is the ccp (Cryptographic Coprocessor) module, which offloads certain cryptographic operations to dedicated hardware. However, a vulnerability has been discovered in the ccp_run_aes_gcm_cmd() function, which can lead to resource leaks.

Vulnerability Detail

The vulnerability in the ccp_run_aes_gcm_cmd() function within the ccp module can result in 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 certain resources, leading to potential memory leaks or file descriptor leaks. Exploiting this vulnerability could allow an attacker to exhaust system resources, leading to denial-of-service conditions or other security implications. The vulnerability was introduced in version v4.12 of the Linux Kernel and has been fixed in version v5.10.71.

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. The recommended approach is to update the Linux Kernel to the fixed version.

Conclusion

The vulnerability in the ccp_run_aes_gcm_cmd() function of the Kernel's ccp module can lead to resource leaks, potentially resulting in denial-of-service conditions or other security implications. It is crucial to update the Linux Kernel to version v5.10.71 or later to fix this vulnerability. By applying the recommended fix, the risk of resource leaks can be eliminated. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can result in resource leaks, potentially leading to denial-of-service conditions or other security implications.

You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you if the vulnerability is present.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.

The exact attack vector for this vulnerability is not specified in the available information. However, it is always advisable to keep systems up to date to minimize the risk of remote exploitation.

The vulnerability is specific to the Kernel's ccp module and does not have any additional dependencies or prerequisites.

Related vulnerabilities

Recent vulnerabilities recorded for 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback