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.

Share this

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.

DistroReleasePackageStatus
Debian13 trixielinuxFixed in 6.12.35-1
12 bookwormlinuxFixed in 6.1.147-1
Ubuntu (+136 more packages)24.04 LTSlinuxFixed in 6.8.0-87.88
22.04 LTSlinuxFixed in 5.15.0-156.166
Red Hat Enterprise LinuxRHEL 10kernelFixed in 6.12.0-55.32.1.el10_0 RHSA-2025:15662
RHEL 9kernelFixed in 5.14.0-570.42.2.el9_6 RHSA-2025:15661
RHEL 8kernelFixed in 4.18.0-553.74.1.el8_10 RHSA-2025:15471
RHEL 8kernel-rtFixed in 4.18.0-553.74.1.rt7.415.el8_10 RHSA-2025:15472
RHEL 6kernelNot 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

  1. Patch todayExploited (KEV)CISA due 2025-09-25

    Operating systemLinux kernel

    Time-of-Check Time-of-Use (TOCTOU) Race ConditionCVE-2025-38352

    Why: Known exploited server software, total technical impact.

Exploit intelligence#

SignalValueSource
Known exploitedYes, added 2025-09-04CISA KEV
Ransomware useUnknownCISA KEV
EPSS (30-day exploitation probability)1.4% (72th pct)FIRST EPSS v2026.06.15
CVSS base score7.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 exploitationactiveCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA 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)#

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.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →