VYPR
Unrated severityNVD Advisory· Published Nov 12, 2025· Updated Apr 15, 2026

CVE-2025-40201

CVE-2025-40201

Description

In the Linux kernel, the following vulnerability has been resolved:

kernel/sys.c: fix the racy usage of task_lock(tsk->group_leader) in sys_prlimit64() paths

The usage of task_lock(tsk->group_leader) in sys_prlimit64()->do_prlimit() path is very broken.

sys_prlimit64() does get_task_struct(tsk) but this only protects task_struct itself. If tsk != current and tsk is not a leader, this process can exit/exec and task_lock(tsk->group_leader) may use the already freed task_struct.

Another problem is that sys_prlimit64() can race with mt-exec which changes ->group_leader. In this case do_prlimit() may take the wrong lock, or (worse) ->group_leader may change between task_lock() and task_unlock().

Change sys_prlimit64() to take tasklist_lock when necessary. This is not nice, but I don't see a better fix for -stable.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A race condition in Linux kernel's sys_prlimit64() allows use-after-free of task_struct via unsafe task_lock(tsk->group_leader) access.

Vulnerability

Description

CVE-2025-40201 is a race condition vulnerability in the Linux kernel's sys_prlimit64() system call, specifically within the do_prlimit() function. The root cause is the unsafe use of task_lock(tsk->group_leader) when the target task (tsk) is not the current task and is not a thread group leader. The get_task_struct(tsk) call only protects the task_struct itself, but if the process exits or execs, the group_leader pointer may point to a freed task_struct`, leading to a use-after-free condition [1].

Exploitation

An attacker can exploit this by invoking sys_prlimit64() on a non-leader thread that is concurrently exiting or performing an exec (mt-exec). This race can cause the kernel to access freed memory or take the wrong lock. Additionally, the ->group_leader pointer can change during the execution of do_prlimit(), potentially between task_lock() and task_unlock(), resulting in inconsistent locking [1]. The attack requires local access and the ability to trigger the race condition.

Impact

Successful exploitation could lead to a denial of service (system crash) or, kernel panic) or potentially arbitrary code execution due to memory corruption. The vulnerability affects the integrity and availability of the system.

Mitigation

The fix, committed to the Linux kernel stable tree, changes sys_prlimit64() to take tasklist_lock when necessary to protect the group_leader pointer. Users should apply the latest kernel updates from their distribution [1]. No workaround is available.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2
  • Linux/Kernelinferred2 versions
    (expand)+ 1 more
    • (no CPE)
    • (no CPE)

Patches

5

Vulnerability mechanics

Synthesis attempt was rejected by the grounding validator. Re-run pending.

References

5

News mentions

0

No linked articles in our index yet.