Memory Leak Vulnerability in mm, slub Package

Kernel Updated 02 Oct 2025

Summary

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

UVI-2021-1001838: mm, slub: fix potential memoryleak in kmem_cache_open(). Affects Kernel versions >= 210e7a43fa905bccafa9bb5966fba1d71f33eb8b, < 568f906340b43120abd6fcc67c37396482f85930. 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 mm, slub package is a component of the Linux Kernel, which is responsible for managing memory allocation and deallocation. It provides a memory management subsystem that allows efficient allocation and deallocation of memory blocks. The slub allocator is a specific memory allocation subsystem within mm, slub that manages the allocation of small memory objects. This vulnerability affects the mm, slub package and can lead to potential memory leaks.

Vulnerability Detail

The vulnerability, identified as UVI-2021-1001838, exists in the kmem_cache_open() function of the mm, slub package. It can result in memory leaks, where allocated memory is not properly deallocated, leading to a gradual depletion of available memory resources. This vulnerability could potentially be exploited by an attacker to exhaust system memory, causing denial-of-service conditions or other adverse effects. The vulnerability was introduced in version v4.8 of the Linux Kernel and has been fixed in version v5.10.76.

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

No specific workaround has been provided for this vulnerability. It is advised to apply the recommended fix by updating the Linux Kernel to the latest version.

Conclusion

The memory leak vulnerability in the mm, slub package can have significant implications for system stability and performance. It is crucial to update the Linux Kernel to version v5.10.76 or later to mitigate this vulnerability. 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 memory leaks, leading to a gradual depletion of available memory resources. This can cause system instability, performance degradation, or denial-of-service conditions.

An attacker could potentially exploit this vulnerability by repeatedly triggering the kmem_cache_open() function, causing memory leaks and exhausting system memory resources.

The vulnerability was introduced in version v4.8 of the Linux Kernel and affects all versions up to v5.10.75.

Yes, the vulnerability has been fixed in version v5.10.76 of the Linux Kernel.

There are no known instances of this vulnerability being exploited in the wild.

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