Memory Leak Vulnerability in perf bench futex

Kernel Updated 02 Oct 2025

Summary

29/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002327: perf bench futex: Fix memory leak of perf_cpu_map__new(). Affects Kernel versions >= 9c3516d1b850ea938b074df33e4c86d721c77720, < 99643bdc6ff1c75ccd2871368fbcd20e8231d77e. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The perf bench futex is a performance benchmarking tool in the Linux Kernel. It is used to measure the performance of futex system calls. Futex is a fast user-space locking mechanism that allows processes to synchronize their operations efficiently. The tool creates a CPU map to track the performance of different CPUs. However, a memory leak vulnerability has been discovered in the perf_cpu_map__new() function, which is used to create the CPU map. This vulnerability can lead to memory exhaustion and potential denial-of-service attacks.

Vulnerability Detail

The memory leak vulnerability in perf bench futex occurs due to a failure to release allocated memory in the perf_cpu_map__new() function. When the function is called multiple times, it allocates memory for the CPU map but fails to free it, resulting in a memory leak. An attacker can exploit this vulnerability by repeatedly triggering the creation of CPU maps, leading to memory exhaustion and potential system instability. The impact of this vulnerability can range from performance degradation to complete system unresponsiveness.

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

As a temporary workaround, users can avoid using the perf bench futex tool or limit its usage to minimize the risk of memory exhaustion. However, this is not a permanent solution and updating the Linux Kernel is strongly advised.

Conclusion

The memory leak vulnerability in perf bench futex can lead to memory exhaustion and potential denial-of-service attacks. It is crucial to update the Linux Kernel to the latest version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

perf bench futex is a performance benchmarking tool in the Linux Kernel used to measure the performance of futex system calls.

A memory leak vulnerability occurs when a program fails to release allocated memory, leading to memory exhaustion and potential system instability.

The impact of this vulnerability can range from performance degradation to complete system unresponsiveness.

To fix this vulnerability, update the Linux Kernel to version v5.15.5 or later.

As a temporary workaround, users can avoid using the perf bench futex tool or limit its usage to minimize the risk of memory exhaustion.

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