Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2025-40341— futex: Don't leak robust_list pointer on exec race

EPSS 0.03% · P11
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-40341

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
futex: Don't leak robust_list pointer on exec race
Source: NVD (National Vulnerability Database)
Vulnerability Description
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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于竞争条件下泄露robust_list指针。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 0771dfefc9e538f077d0b43b6dec19a5a67d0e70 ~ 6511984d1aa1360181bcafb1ca75df7f291ef237 -
LinuxLinux 2.6.17 -

II. Public POCs for CVE-2025-40341

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-40341

登录查看更多情报信息。

Same Patch Batch · Linux · 2025-12-09 · 152 CVEs total

CVE-2023-53826ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show()
CVE-2023-53845nilfs2: fix infinite loop in nilfs_mdt_get_block()
CVE-2023-53844drm/ttm: Don't leak a resource on swapout move error
CVE-2023-53843net: openvswitch: reject negative ifindex
CVE-2023-53842ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove
CVE-2023-53841devlink: report devlink_port_type_warn source device
CVE-2023-53840usb: early: xhci-dbc: Fix a potential out-of-bound memory access
CVE-2023-53839dccp: fix data-race around dp->dccps_mss_cache
CVE-2023-53838f2fs: synchronize atomic write aborts
CVE-2023-53837drm/msm: fix NULL-deref on snapshot tear down
CVE-2023-53836bpf, sockmap: Fix skb refcnt race after locking changes
CVE-2023-53834iio: adc: ina2xx: avoid NULL pointer dereference on OF device match
CVE-2023-53833drm/i915: Fix NULL ptr deref by checking new_crtc_state
CVE-2023-53832md/raid10: fix null-ptr-deref in raid10_sync_request
CVE-2023-53831net: read sk->sk_family once in sk_mc_loop()
CVE-2023-53830platform/x86: think-lmi: Fix memory leak when showing current settings
CVE-2023-53829f2fs: flush inode if atomic file is aborted
CVE-2023-53828Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor()
CVE-2023-53827Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp}
CVE-2022-50674riscv: vdso: fix NULL deference in vdso_join_timens() when vfork

Showing top 20 of 152 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2025-40341

No comments yet


Leave a comment