Memory Leak Vulnerability in perf bench futex

Kernel Updated 02 Oct 2025

Summary

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

UVI-2021-1002287: perf bench futex: Fix memory leak of perf_cpu_map__new(). Affects Kernel versions >= 9c3516d1b850ea938b074df33e4c86d721c77720, < 2ada5c0877f4aa9b0749e7777557d9a5d2973082. 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 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 efficient synchronization between threads. The tool creates multiple threads and performs futex operations to evaluate their performance. However, a memory leak vulnerability has been discovered in the perf_cpu_map__new() function used by perf bench futex.

Vulnerability Detail

The memory leak vulnerability in perf_cpu_map__new() can lead to the exhaustion of system memory resources. When the function is called, it allocates memory for a new perf_cpu_map structure but fails to free it properly, resulting in a memory leak. This can cause a gradual depletion of available memory, leading to performance degradation and potentially denial-of-service conditions. The vulnerability was introduced in Linux Kernel version v5.4 and fixed in version v5.10.82.

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 workaround, users can avoid using the perf bench futex tool until the Linux Kernel is updated to a version that includes the fix for this vulnerability.

Conclusion

The memory leak vulnerability in perf bench futex's perf_cpu_map__new() function can lead to the exhaustion of system memory resources. It is crucial to update the Linux Kernel to version v5.10.82 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

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 a gradual depletion of available memory resources.

The memory leak vulnerability in perf_cpu_map__new() can result in the exhaustion of system memory resources, leading to performance degradation and potential denial-of-service conditions.

The vulnerability was introduced in Linux Kernel version v5.4 and fixed in version v5.10.82.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.82 or later, which includes the necessary fix.

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