Linux Kernel up to 6.1.158/6.6.116/6.12.57/6.17.7 futex sys_get_robust_list memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.6$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.1.158/6.6.116/6.12.57/6.17.7. It has been classified as critical. Affected by this issue is the function sys_get_robust_list of the component futex. This manipulation causes memory leak. This vulnerability is registered as CVE-2025-40341. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.1.158/6.6.116/6.12.57/6.17.7 and classified as critical. Affected by this vulnerability is the function sys_get_robust_list of the component futex. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: futex: Don't leak robust_list pointer on exec race sys_get_robust_list() and compat_get_robust_list() use ptrace_may_access() to check if the calling task is allowed to access another task's robust_list pointer. This check is racy against a concurrent exec() in the target process. During exec(), a task may transition from a non-privileged binary to a privileged one (e.g., setuid binary) and its credentials/memory mappings may change. If get_robust_list() performs ptrace_may_access() before this transition, it may erroneously allow access to sensitive information after the target becomes privileged. A racy access allows an attacker to exploit a window during which ptrace_may_access() passes before a target process transitions to a privileged state via exec(). For example, consider a non-privileged task T that is about to execute a setuid-root binary. An attacker task A calls get_robust_list(T) while T is still unprivileged. Since ptrace_may_access() checks permissions based on current credentials, it succeeds. However, if T begins exec immediately afterwards, it becomes privileged and may change its memory mappings. Because get_robust_list() proceeds to access T->robust_list without synchronizing with exec() it may read user-space pointers from a now-privileged process. This violates the intended post-exec access restrictions and could expose sensitive memory addresses or be used as a primitive in a larger exploit chain. Consequently, the race can lead to unauthorized disclosure of information across privilege boundaries and poses a potential security risk. Take a read lock on signal->exec_update_lock prior to invoking ptrace_may_access() and accessing the robust_list/compat_robust_list. This ensures that the target task's exec state remains stable during the check, allowing for consistent and synchronized validation of credentials.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2025-40341 since 04/16/2025. The exploitation appears to be difficult. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 282382 (Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2025-1350)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.159, 6.6.117, 6.12.58 or 6.17.8 eliminates this vulnerability. Applying the patch 6511984d1aa1360181bcafb1ca75df7f291ef237/4aced32596ead1820b7dbd8e40d30b30dc1f3ad4/3b4222494489f6d4b8705a496dab03384b7ca998/b524455a51feb6013df3a5dba3160487b2e8e22a/6b54082c3ed4dc9821cdf0edb17302355cc5bb45 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (282382). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 282382
Nessus Name: Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2025-1350)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.159/6.6.117/6.12.58/6.17.8
Patch: 6511984d1aa1360181bcafb1ca75df7f291ef237/4aced32596ead1820b7dbd8e40d30b30dc1f3ad4/3b4222494489f6d4b8705a496dab03384b7ca998/b524455a51feb6013df3a5dba3160487b2e8e22a/6b54082c3ed4dc9821cdf0edb17302355cc5bb45

Timelineinfo

04/16/2025 CVE reserved
12/09/2025 +237 days Advisory disclosed
12/09/2025 +0 days VulDB entry created
01/08/2026 +30 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-40341 (🔒)
GCVE (CVE): GCVE-0-2025-40341
GCVE (VulDB): GCVE-100-334885

Entryinfo

Created: 12/09/2025 07:35
Updated: 01/08/2026 20:30
Changes: 12/09/2025 07:35 (59), 01/08/2026 20:30 (2)
Complete: 🔍
Cache ID: 216:0C0:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!