CVE-2025-38352
Linux — Linux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition Vulnerability
Linux · CWE-367 · in CISA KEV since 2025-09-04
EVRS 75 of 100 Urgent
Patch This Cycle
Rank 1,275 of 2,960 tracked
Raised to the floor for a confirmed exploited vulnerability.
Why it scores 75
Evidence available: 6 of 7 signalsListed in the CISA KEV catalog, and an EPSS probability of 0.013.
- CISA KEVApplied
- RansomwareDid not apply
- Vendor exploitationDid not apply
- EPSSApplied
- Microsoft Exploitability IndexNot applicable
- Pre-patch disclosureNo data
- KEV recencyDid not apply
- CVSSApplied
The band answers “how soon”, not “how bad”. No data for: Pre-patch disclosure. Why some signals show no data
Fix
Patch or fixed version identifiedCISA required action
- This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. Please check with specific vendors for information on patching status. For more information, please see
- source.android.com/…/2025-09-01
- nvd.nist.gov/…/CVE-2025-38352
Fixed in
linux -> 6.1.147-1 | linux -> 6.12.35-1
Affected versions
- linux kernel
>= 2.6.36 < 5.4.295>= 5.5 < 5.10.239>= 5.11 < 5.15.186>= 5.16 < 6.1.142>= 6.2 < 6.6.94>= 6.7 < 6.12.34>= 6.13 < 6.15.36.16 - debian linux
11.0
Remediation
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Fixed versions from NVD.
Evidence
Each value with its source| Measure | Value | Source |
|---|---|---|
| CVSS base scoreHow severe the flaw is in itself. It does not say how likely an attack is. | 7.8 | NVD |
| FIRST EPSSFIRST's estimate of the chance this is exploited in the next 30 days, and how that ranks against all CVEs. | 0.013 (71.1st pctl) | FIRST EPSS |
| Actively exploitedWhether a source of record has confirmed attacks using it in the wild. | Confirmed | CISA KEV |
| Ransomware campaign useWhether CISA has seen ransomware operators use it. | Unknown or none | CISA KEV |
| CISA remediation deadlineThe date US federal agencies must have fixed or mitigated it. | 2025-09-25 · KEV since 2025 · listed over a year | CISA KEV |
| Public exploit moduleA module existing is not the same as active exploitation. | None known | Metasploit |
| EUVD cross-referenceENISA's record: CVSS 7.8 (v3.1), assigned by Linux. | Listed | ENISA EUVD |
Description
NVDIn 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.
What CISA says to do