CVE-2025-38352
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and…
Browse: All 2025 CVEs · All vendors
- CVSS score
- 7.8 High
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- CISA KEV
- Yes — actively exploited (added 2025-09-04, remediation due 2025-09-25)
- Weakness (CWE)
- CWE-367
- Published
- 2025-07-22
- Last modified
- 2026-07-30
- NVD status
- Analyzed
Description
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.
Affected products
- linux linux kernel
- debian debian linux
Affected ranges per NVD CPE data; confirm exact versions in the vendor advisory.
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Federal remediation deadline: 2025-09-25.
How to prioritize this
This vulnerability is on the CISA KEV list, meaning it is being actively exploited — treat it as urgent regardless of the raw CVSS number. Use the live CVE lookup for the latest NVD data, and the CVSS 3.1 calculator to model your own environmental score.
References
- https://git.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff
- https://git.kernel.org/stable/c/2f3daa04a9328220de46f0d5c919a6c0073a9f0b
- https://git.kernel.org/stable/c/460188bc042a3f40f72d34b9f7fc6ee66b0b757b
- https://git.kernel.org/stable/c/764a7a5dfda23f69919441f2eac2a83e7db6e5bb
- https://git.kernel.org/stable/c/78a4b8e3795b31dae58762bc091bb0f4f74a2200
- https://git.kernel.org/stable/c/c076635b3a42771ace7d276de8dc3bc76ee2ba1b
- https://git.kernel.org/stable/c/c29d5318708e67ac13c1b6fc1007d179fb65b4d7
- https://git.kernel.org/stable/c/f90fff1e152dedf52b932240ebbd670d83330eca
FAQ
Is CVE-2025-38352 actively exploited?
Yes. CISA added CVE-2025-38352 to its Known Exploited Vulnerabilities (KEV) catalog on 2025-09-04, with a federal remediation deadline of 2025-09-25. A KEV listing means real-world exploitation is confirmed, so patching this should be prioritized above many higher-CVSS bugs that aren't being exploited.
What is the CVSS score of CVE-2025-38352?
CVE-2025-38352 has a CVSS base score of 7.8 (High). Its vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Related vulnerabilities
- CVE-2026-53362 — Linux Kernel
- CVE-2022-0995 — Linux Kernel
- CVE-2022-0492 — Linux Kernel
- CVE-2026-31431 — Linux Kernel
- CVE-2018-14634 — Linux Kernel
- CVE-2021-22555 — Linux Kernel
Data source: NVD & CISA KEV. Shown as-is; nothing added. Last generated from NVD data — re-check the live tool for updates.
weekly kev brief
Patch what's actually being exploited.
One email a week: the KEV additions that matter, prioritized — no noise.
Free. No spam. Unsubscribe anytime. Delivered by Beehiiv.