Live › vulnerability › CVE-2025-38352
Go to dashboardA race condition in the Linux kernel lets a local process change data between a check and its use, which can affect confidentiality, integrity and availability. CISA lists it as actively exploited in the wild.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| linux kernel | vendor | >= 2.6.36, < 5.4.295 | 5.4.295 |
| linux kernel | vendor | >= 5.5, < 5.10.239 | 5.10.239 |
| linux kernel | vendor | >= 5.11, < 5.15.186 | 5.15.186 |
| linux kernel | vendor | >= 5.16, < 6.1.142 | 6.1.142 |
| linux kernel | vendor | >= 6.2, < 6.6.94 | 6.6.94 |
| linux kernel |
| vendor |
| >= 6.7, < 6.12.34 |
| 6.12.34 |
| linux kernel | vendor | >= 6.13, < 6.15.3 | 6.15.3 |
| linux kernel | vendor | = 6.16 | – |
| debian linux | vendor | = 11.0 | – |
| Linux Kernel | vendor | – | – |
Unknown from the sources.
Apply the kernel vendor's mitigation or patch per CISA guidance; discontinue use of the product if no mitigation is available.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2025-38352")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.