CVE-2025-40341
BaseFortify
Publication date: 2025-12-09
Last updated on: 2025-12-09
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves a race condition in the Linux kernel's futex subsystem where the functions sys_get_robust_list() and compat_get_robust_list() check permissions to access another task's robust_list pointer using ptrace_may_access(). The check is racy against a concurrent exec() call in the target process. During exec(), a process may change from non-privileged to privileged (e.g., executing a setuid binary), changing its credentials and memory mappings. If the permission check happens before this transition but the access happens after, it can lead to unauthorized access to sensitive information from a now-privileged process. This race condition can expose sensitive memory addresses or be used in larger exploit chains, violating intended access restrictions across privilege boundaries.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to gain unauthorized access to sensitive information by exploiting a timing window during which permission checks pass before a target process becomes privileged. This can lead to information disclosure of memory addresses or other sensitive data from privileged processes, potentially enabling further exploitation or privilege escalation.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the Linux kernel to a version where the fix has been applied. The fix involves taking a read lock on signal->exec_update_lock prior to invoking ptrace_may_access() and accessing the robust_list/compat_robust_list, ensuring stable exec state and synchronized validation of credentials. Applying the kernel patch or upgrading to a fixed kernel version will prevent the race condition and unauthorized disclosure of information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can lead to unauthorized disclosure of sensitive information across privilege boundaries due to a race condition in access checks during process execution. Such unauthorized disclosure of sensitive data could potentially violate compliance requirements of standards and regulations like GDPR and HIPAA, which mandate protection of sensitive information and prevention of unauthorized access. Therefore, exploitation of this vulnerability may negatively impact compliance with these regulations.