CVE-2025-38352

Confirmed PUBLISHED

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

Linux · Linux

1 day faster than CISA KEV

Exploited in the wild

Recommended Action

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Confidence
Confirmed
Exploitation Status
Exploited in the wild
Observed in Sensors
No
Attempts (30d)
Unique Attacker IPs
CISA KEV
In CISA KEV
CVSS / EPSS
7.4 High EPSS 1.3%

At a Glance

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.

cisa linux
CVE Published
Jul 22, 2025
Exploitation Reported
Jun 01, 2026
CVSS
7.4 High
EPSS
1.3%
No user interaction Unauthenticated

Affected Versions

Vendor Product Version Status
Linux
Linux

0bdd2ed4138ec04e09b4f8165981efc99e439f55 to < 78a4b8e3795b31dae58762bc091bb0f4f74a2200

Affected
Linux
Linux

0bdd2ed4138ec04e09b4f8165981efc99e439f55 to < c076635b3a42771ace7d276de8dc3bc76ee2ba1b

Affected
Linux
Linux

0bdd2ed4138ec04e09b4f8165981efc99e439f55 to < 2f3daa04a9328220de46f0d5c919a6c0073a9f0b

Affected
Linux
Linux

0bdd2ed4138ec04e09b4f8165981efc99e439f55 to < 764a7a5dfda23f69919441f2eac2a83e7db6e5bb

Affected
Linux
Linux

0bdd2ed4138ec04e09b4f8165981efc99e439f55 to < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff

Affected
Linux
Linux

0bdd2ed4138ec04e09b4f8165981efc99e439f55 to < c29d5318708e67ac13c1b6fc1007d179fb65b4d7

Affected
Linux
Linux

0bdd2ed4138ec04e09b4f8165981efc99e439f55 to < 460188bc042a3f40f72d34b9f7fc6ee66b0b757b

Affected
Linux
Linux

0bdd2ed4138ec04e09b4f8165981efc99e439f55 to < f90fff1e152dedf52b932240ebbd670d83330eca

Affected
Linux
Linux

2.6.36

Affected
Linux
Linux

0 to < 2.6.36

Unaffected
Linux
Linux

5.4.295 to <= 5.4.*

Unaffected
Linux
Linux

5.10.239 to <= 5.10.*

Unaffected
Linux
Linux

5.15.186 to <= 5.15.*

Unaffected
Linux
Linux

6.1.142 to <= 6.1.*

Unaffected
Linux
Linux

6.6.94 to <= 6.6.*

Unaffected
Linux
Linux

6.12.34 to <= 6.12.*

Unaffected
Linux
Linux

6.15.3 to <= 6.15.*

Unaffected
Linux
Linux

6.16 to <= *

Unaffected

CVE References

Show 3 more references

Recommended Actions

  • Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
  • Use the Pro API to automate enrichment, telemetry, and workflow delivery for VM, SOC, and CTI pipelines.