Mismatch between reconstructed freelist depth and cnt in mm, slub

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001816: mm, slub: fix mismatch between reconstructed freelist depth and cnt. Affects Kernel versions >= c3895391df385c6628638f014c87e16f5e2efd45, < a1ec195a1943c39fffa96e47ab6532d74a9f4c78. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the operating system that manages system resources and provides an interface for software to interact with the hardware. The specific vulnerability is related to the mm (memory management) subsystem and the slub allocator. The slub allocator is responsible for managing kernel memory allocations. The vulnerability arises from a mismatch between the reconstructed freelist depth and the cnt value. This mismatch can lead to memory corruption and potential security vulnerabilities.

Vulnerability Detail

The vulnerability occurs due to a mismatch between the reconstructed freelist depth and the cnt value in the slub allocator. This mismatch can result in memory corruption and potential security vulnerabilities. An attacker may be able to exploit this vulnerability to gain unauthorized access, execute arbitrary code, or cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet.

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 solution is to update the Kernel to the fixed version.

Conclusion

The vulnerability in the mm, slub allocator of the Kernel package can lead to memory corruption and potential security vulnerabilities. It is recommended to update the Kernel to the fixed version (v5.4.156) to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The Kernel is the core component of the operating system that manages system resources and provides an interface for software to interact with the hardware.

The mm (memory management) subsystem in the Kernel is responsible for managing system memory, including allocation and deallocation of memory resources.

The slub allocator is a memory allocator in the Kernel that manages kernel memory allocations.

Memory corruption refers to the unintended modification of data in memory, which can lead to program crashes, security vulnerabilities, and unpredictable behavior.

The process of updating the Kernel depends on the specific Linux distribution. Generally, it involves using package management tools or manually compiling and installing the updated Kernel version.

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