Back to CVE records
High 7.8Known exploited (CISA KEV)Published Jul 22, 2025

CVE-2025-38352posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()

Updated under an hour ago ()

Does this affect you?

It affects Linux and 2 other products. Add what you run to find out whether that includes you.

CISA lists it as known exploited since Sep 4, 2025; federal agencies had to remediate by Sep 25, 2025. Treat that date as your deadline.

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
7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-367
Known exploited
Added to CISA KEV Sep 4, 2025; federal remediation due Sep 25, 2025Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
EPSS (exploitation in the next 30 days)
1.34% (percentile 71)
Assigned by
Linux
NVD analysis
Analyzed
Record last updated
Sep 8, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from 0bdd2ed4138ec04e09b4f8165981efc99e439f55 before 78a4b8e3795b31dae58762bc091bb0f4f74a2200; from 0bdd2ed4138ec04e09b4f8165981efc99e439f55 before c076635b3a42771ace7d276de8dc3bc76ee2ba1b; from 0bdd2ed4138ec04e09b4f8165981efc99e439f55 before 2f3daa04a9328220de46f0d5c919a6c0073a9f0b; from 0bdd2ed4138ec04e09b4f8165981efc99e439f55 before 764a7a5dfda23f69919441f2eac2a83e7db6e5bb; from 0bdd2ed4138ec04e09b4f8165981efc99e439f55 before 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff; from 0bdd2ed4138ec04e09b4f8165981efc99e439f55 before c29d5318708e67ac13c1b6fc1007d179fb65b4d7; from 0bdd2ed4138ec04e09b4f8165981efc99e439f55 before 460188bc042a3f40f72d34b9f7fc6ee66b0b757b; from 0bdd2ed4138ec04e09b4f8165981efc99e439f55 before f90fff1e152dedf52b932240ebbd670d83330eca
CNA record
linux linux_kernel
linux:linux_kernel
from 2.6.36 before 5.4.295; from 5.5 before 5.10.239; from 5.11 before 5.15.186; from 5.16 before 6.1.142; from 6.2 before 6.6.94; from 6.7 before 6.12.34; from 6.13 before 6.15.3; 6.16
NVD
debian debian_linux
debian:debian_linux
11.0
NVD

References

  • patch
  • patch
  • patch
  • patch
  • patch
  • patch
  • patch
  • patch
  • mailing-list, third-party-advisory
  • mailing-list, third-party-advisory
  • exploit
  • us-government-resource

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.