CVE-2025-40201 json
kernel/sys.c: fix the racy usage of task_lock(tsk->group_leader) in sys_prlimit64() paths
published 11mo ago modified 21d ago also EUVD-2025-150373
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.157, 6.6.113, 6.12.54, 6.17.4, 6.18
- linux Debian 12 6.1.158-1
- linux Debian 13 6.12.57-1
- linux Debian 14 6.17.6-1
debian advisories DEBIAN-CVE-2025-40201
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux Ubuntu 25.10 6.17.0-14.14
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-aws Ubuntu 25.10 6.17.0-1007.7
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
- linux-gcp Ubuntu 25.10 6.17.0-1007.7
- linux-gke Ubuntu 24.04 LTS 6.8.0-1048.53
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1049.49
ubuntu advisories UBUNTU-CVE-2025-40201
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1 6.4.0-41.1
- kernel-source-rt Linux Micro 6.1 6.4.0-41.1
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-41.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-41.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-41.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-41.1.21.18
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.34.1
suse advisories SUSE-SU-2026:21255-1SUSE-SU-2026:21123-1SUSE-SU-2026:21114-1SUSE-SU-2026:1081-1SUSE-SU-2026:0962-1SUSE-SU-2026:20012-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.8.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-kvmsmall openSUSE Leap 16.0 6.12.0-160000.8.1
opensuse advisories openSUSE-SU-2025:20172-1
- git.kernel.org/stable/c/1bc0d9315ef5296abb2c9fd840336255850ded18 commit
- git.kernel.org/stable/c/132f827e7bac7373e1522e89709d70b43cae5342 commit
- git.kernel.org/stable/c/19b45c84bd9fd42fa97ff80c6350d604cb871c75 commit
- git.kernel.org/stable/c/6796412decd2d8de8ec708213bbc958fab72f143 commit
- git.kernel.org/stable/c/a15f37a40145c986cdf289a4b88390f35efdecc4 commit
Is CVE-2025-40201 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-40201 updated cvss 5.8
kernel: kernel/sys.c: fix the racy usage of task_lock(tsk->group_leader) in sys_prlimit64() paths
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 25d ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/1bc0d9315ef5296abb2c9fd840336255850ded18
- git.kernel.org /stable/c/132f827e7bac7373e1522e89709d70b43cae5342
- git.kernel.org /stable/c/19b45c84bd9fd42fa97ff80c6350d604cb871c75
- git.kernel.org /stable/c/6796412decd2d8de8ec708213bbc958fab72f143
- git.kernel.org /stable/c/a15f37a40145c986cdf289a4b88390f35efdecc4
Sources
- CVE List CVE-2025-40201
- NVD CVE-2025-40201
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.