Memory Leak Vulnerability in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

31/05/2021

Disclosed on

N/A

Severity

No i

Fix available

Unrated

Severity

Not published

CVSS Score

GSD-2021-1000339: KEYS: trusted: Fix memory leak on object td. Affects Kernel versions >= 9d83cc1a1e7f494aedee2aa108e801d11525fccf, < 31c9a4b24d86cbb36ff0d7a085725a3b4f0138c8. 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 Browse

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.

Background

The Linux Kernel is the core component of the Linux operating system. It provides essential functionality and interfaces for various hardware devices and software applications. The trusted subsystem in the Linux Kernel is responsible for managing trusted keys and objects. These trusted objects are used for secure communication and authentication within the system. However, a memory leak vulnerability has been discovered in the trusted subsystem, specifically in the handling of object td.

Vulnerability Detail

The memory leak vulnerability in the Linux Kernel's trusted subsystem can be exploited by an attacker to exhaust system memory resources. By repeatedly creating and deleting trusted objects, an attacker can cause the system to run out of memory, leading to a denial-of-service condition. This vulnerability can be particularly dangerous in systems with limited memory resources. The vulnerability was introduced in version v5.10.20 of the Linux Kernel and has been fixed in version v5.10.38.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.38 or later. This update includes a patch that addresses the memory leak issue in the trusted subsystem. Users can obtain the updated kernel from the official Linux Kernel repository.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the patch provided in the updated version of the Linux Kernel to mitigate the risk of memory exhaustion.

Conclusion

The memory leak vulnerability in the Linux Kernel's trusted subsystem can be mitigated by updating to version v5.10.38 or later. It is recommended to apply the patch provided in the updated version to prevent memory exhaustion and potential denial-of-service attacks. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →