# CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()

> CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del(). CVSS 7.8 (CVSS 3.1), in CISA KEV.

Canonical: https://rewindex.com/cve/CVE-2025-38352
Last updated: 2026-09-08T18:17:32Z

- Published: 2025-07-22 08:04 UTC · Updated: 2026-09-08 18:17 UTC · Assigner: Linux
- CVSS: 7.8 (CVSS 3.1) · Severity: High · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS: 1.4%, 71th percentile (scored 2026-10-25)
- CISA KEV: yes, added 2025-09-04, federal due date 2025-09-25, ransomware use: Unknown

## 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.

## CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

## Affected vendors and products

- Linux: Linux

## References

- [CVE record on cve.org](https://www.cve.org/CVERecord?id=CVE-2025-38352)
- [NVD entry](https://nvd.nist.gov/vuln/detail/CVE-2025-38352)
- [https://git.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff](https://git.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff)
- [https://git.kernel.org/stable/c/2f3daa04a9328220de46f0d5c919a6c0073a9f0b](https://git.kernel.org/stable/c/2f3daa04a9328220de46f0d5c919a6c0073a9f0b)
- [https://git.kernel.org/stable/c/460188bc042a3f40f72d34b9f7fc6ee66b0b757b](https://git.kernel.org/stable/c/460188bc042a3f40f72d34b9f7fc6ee66b0b757b)
- [https://git.kernel.org/stable/c/764a7a5dfda23f69919441f2eac2a83e7db6e5bb](https://git.kernel.org/stable/c/764a7a5dfda23f69919441f2eac2a83e7db6e5bb)
- [https://git.kernel.org/stable/c/78a4b8e3795b31dae58762bc091bb0f4f74a2200](https://git.kernel.org/stable/c/78a4b8e3795b31dae58762bc091bb0f4f74a2200)
- [https://git.kernel.org/stable/c/c076635b3a42771ace7d276de8dc3bc76ee2ba1b](https://git.kernel.org/stable/c/c076635b3a42771ace7d276de8dc3bc76ee2ba1b)
- [https://git.kernel.org/stable/c/c29d5318708e67ac13c1b6fc1007d179fb65b4d7](https://git.kernel.org/stable/c/c29d5318708e67ac13c1b6fc1007d179fb65b4d7)
- [https://git.kernel.org/stable/c/f90fff1e152dedf52b932240ebbd670d83330eca](https://git.kernel.org/stable/c/f90fff1e152dedf52b932240ebbd670d83330eca)

---

_Sources: CVE records from the CVE Program (cve.org). CVE® is a registered trademark of The MITRE Corporation. (https://www.cve.org/) This product uses data from the NVD API but is not endorsed or certified by the NVD. (https://nvd.nist.gov/) Known Exploited Vulnerabilities catalog from CISA. (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) EPSS scores from FIRST (Exploit Prediction Scoring System). (https://www.first.org/epss/)_


---
Canonical: https://rewindex.com/cve/CVE-2025-38352 · Markdown: https://rewindex.com/cve/CVE-2025-38352.md · JSON: https://rewindex.com/api/v1/cves/CVE-2025-38352 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-10-26T02:13:20.052Z