# CVE-2025-38352

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.

- Page: https://www.vulneraibility.com/cve/CVE-2025-38352
- CVSS: 7.8
- Known exploited: yes, in CISA KEV since 2025-09-04; CISA due date 2025-09-25
- EPSS: 1.36%
- Unvetted proof-of-concept code on GitHub: 6 GitHub proofs of concept (first 2025-12-21)
- CISA SSVC: exploitation active, automatable no, technical impact total (assessed 2025-09-05)
- Weakness: CWE-367
- Published: 2025-07-22

## Affected versions

- Linux: affected >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 78a4b8e3795b31dae58762bc091bb0f4f74a2200; >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < c076635b3a42771ace7d276de8dc3bc76ee2ba1b; >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 2f3daa04a9328220de46f0d5c919a6c0073a9f0b; >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 764a7a5dfda23f69919441f2eac2a83e7db6e5bb; >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff; >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < c29d5318708e67ac13c1b6fc1007d179fb65b4d7; >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 460188bc042a3f40f72d34b9f7fc6ee66b0b757b; >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < f90fff1e152dedf52b932240ebbd670d83330eca; 2.6.36; fixed in < 2.6.36, >= 5.4.295 and <= 5.4.*, >= 5.10.239 and <= 5.10.*, >= 5.15.186 and <= 5.15.*, >= 6.1.142 and <= 6.1.*, >= 6.6.94 and <= 6.6.*, >= 6.12.34 and <= 6.12.*, >= 6.15.3 and <= 6.15.*, >= 6.16 and <= *

A version outside these ranges is not a statement that it is unaffected.

## References

- [other] https://git.kernel.org/stable/c/78a4b8e3795b31dae58762bc091bb0f4f74a2200
- [other] https://git.kernel.org/stable/c/c076635b3a42771ace7d276de8dc3bc76ee2ba1b
- [other] https://git.kernel.org/stable/c/2f3daa04a9328220de46f0d5c919a6c0073a9f0b
- [other] https://git.kernel.org/stable/c/764a7a5dfda23f69919441f2eac2a83e7db6e5bb
- [other] https://git.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff
- [other] https://git.kernel.org/stable/c/c29d5318708e67ac13c1b6fc1007d179fb65b4d7
- [other] https://git.kernel.org/stable/c/460188bc042a3f40f72d34b9f7fc6ee66b0b757b
- [other] https://git.kernel.org/stable/c/f90fff1e152dedf52b932240ebbd670d83330eca
- [other] https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-38352
- [exploit] https://github.com/farazsth98/chronomaly
- [other] https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- [other] https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html

---
Summary, impact and action are written by the vulneraibility.com AI analysis pipeline from the CVE record, NVD, CISA and FIRST data; verify against the references.