Linux · Linux kernel · CWE-367 · published 2025-07-22
CVE-2025-38352Linux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition Vulnerability
Patch today Known exploited server software, total technical impact.
CVE-2025-38352 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2025-09-04. EPSS estimates a 1.4% chance of exploitation in the next 30 days, higher than 72% of all CVEs. This Linux kernel vulnerability: CVSS 7.8 (v3.1), a successful attack gives total control of the component. Patched packages are out for Debian, Ubuntu and Red Hat Enterprise Linux. US federal agencies must remediate by 2025-09-25. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
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. (federal due date 2025-09-25)
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | linux | Fixed in 6.12.35-1 |
| 12 bookworm | linux | Fixed in 6.1.147-1 | |
| Ubuntu (+136 more packages) | 24.04 LTS | linux | Fixed in 6.8.0-87.88 |
| 22.04 LTS | linux | Fixed in 5.15.0-156.166 | |
| Red Hat Enterprise Linux | RHEL 10 | kernel | Fixed in 6.12.0-55.32.1.el10_0 RHSA-2025:15662 |
| RHEL 9 | kernel | Fixed in 5.14.0-570.42.2.el9_6 RHSA-2025:15661 | |
| RHEL 8 | kernel | Fixed in 4.18.0-553.74.1.el8_10 RHSA-2025:15471 | |
| RHEL 8 | kernel-rt | Fixed in 4.18.0-553.74.1.rt7.415.el8_10 RHSA-2025:15472 | |
| RHEL 6 | kernel | Not affected |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Operating systemLinux kernel
Time-of-Check Time-of-Use (TOCTOU) Race ConditionCVE-2025-38352
Why: Known exploited server software, total technical impact.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2025-09-04 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 1.4% (72th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.8 (v3.1)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
More from this vendor: all Linux vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Linux Linux
0bdd2ed4138ec04e09b4f8165981efc99e439f55to before78a4b8e3795b31dae58762bc091bb0f4f74a2200(affected)0bdd2ed4138ec04e09b4f8165981efc99e439f55to beforec076635b3a42771ace7d276de8dc3bc76ee2ba1b(affected)0bdd2ed4138ec04e09b4f8165981efc99e439f55to before2f3daa04a9328220de46f0d5c919a6c0073a9f0b(affected)0bdd2ed4138ec04e09b4f8165981efc99e439f55to before764a7a5dfda23f69919441f2eac2a83e7db6e5bb(affected)0bdd2ed4138ec04e09b4f8165981efc99e439f55to before2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff(affected)0bdd2ed4138ec04e09b4f8165981efc99e439f55to beforec29d5318708e67ac13c1b6fc1007d179fb65b4d7(affected)0bdd2ed4138ec04e09b4f8165981efc99e439f55to before460188bc042a3f40f72d34b9f7fc6ee66b0b757b(affected)0bdd2ed4138ec04e09b4f8165981efc99e439f55to beforef90fff1e152dedf52b932240ebbd670d83330eca(affected)
- Linux Linux
2.6.36(affected)0to before2.6.36(unaffected)5.4.295through5.4.*(unaffected)5.10.239through5.10.*(unaffected)5.15.186through5.15.*(unaffected)6.1.142through6.1.*(unaffected)6.6.94through6.6.*(unaffected)6.12.34through6.12.*(unaffected)6.15.3through6.15.*(unaffected)6.16through*(unaffected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.