Vulnerability record · CVE-2025-38352 · published 22 July 2025
CVE-2025-38352: Linux kernel POSIX CPU timer TOCTOU race enables local privilege escalation
Linux · Linux Kernel
A time-of-check to time-of-use race exists in the Linux kernel between handle_posix_cpu_timers() and posix_cpu_timer_del(). When an exiting non-autoreaping task has passed exit_notify() and runs handle_posix_cpu_timers() from IRQ, a concurrent posix_cpu_timer_del() can fail to observe timer->it.cpu.firing != 0 because cpu_timer_task_rcu() or lock_task_sighand() fails, leading to use-after-free style corruption. The fix adds a tsk->exit_state check in run_posix_cpu_timers().
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Automated analysis
high priorityCISA KEV listing plus a public exploit reference and high CVSS impact make this a high-priority local privilege escalation risk despite the low EPSS probability.
What it is
A time-of-check to time-of-use race exists in the Linux kernel between handle_posix_cpu_timers() and posix_cpu_timer_del(). When an exiting non-autoreaping task has passed exit_notify() and runs handle_posix_cpu_timers() from IRQ, a concurrent posix_cpu_timer_del() can fail to observe timer->it.cpu.firing != 0 because cpu_timer_task_rcu() or lock_task_sighand() fails, leading to use-after-free style corruption. The fix adds a tsk->exit_state check in run_posix_cpu_timers().
Impact
A local attacker can corrupt kernel state and potentially gain code execution or cause a denial of service with high confidentiality, integrity and availability impact.
Attack surface
Reached locally through POSIX CPU timer operations on a task that is exiting; the CVSS vector is AV:L/AC:L/PR:L/UI:N, so low-privileged local access is required and no user interaction is needed.
Exploitation
CVE-2025-38352 is listed in CISA KEV with a due date of 2025-09-25, and a public exploit reference (chronomaly) is present, indicating active exploitation. EPSS 30-day probability is 0.01254 (67.98th percentile), so mass scanning is unlikely but targeted use is plausible.
What to do
- Apply the upstream Linux kernel patches referenced in the git.kernel.org stable commits and update to a fixed kernel version.
- For Debian, apply the fixes announced in the debian-lts-announce mailing list advisories.
- If patching is not immediately possible, restrict local shell and process access to trusted users and monitor for suspicious POSIX timer activity.
- Follow CISA BOD 22-01 guidance for cloud services and discontinue use of affected kernels where mitigations are unavailable.
Detection
- Monitor for kernel crashes or oopses referencing posix_cpu_timer_del, handle_posix_cpu_timers, or run_posix_cpu_timers.
- Audit local processes that create and delete POSIX CPU timers on exiting tasks, especially non-autoreaping children.
- Track CISA KEV status and correlate with host telemetry for known exploit artifacts such as the chronomaly project.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Exploitation in the wild
CISA added CVE-2025-38352 to the Known Exploited Vulnerabilities catalog on 4 September 2025 as "Linux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition Vulnerability". 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. Federal deadline 25 September 2025.
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2025-38352 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2025-38352), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.