---
id: "CVE-2025-38352"
kind: "vulnerability"
aliases: ["CVE-2025-38352"]
title: "In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between\u2026"
severity: "high"
cvss: 7.8
epss: null
exploited: true
status: "open"
category: "infrastructure"
products: [{"name": "linux kernel", "fixed": ["5.4.295"], "affected": ">= 2.6.36, < 5.4.295", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["5.10.239"], "affected": ">= 5.5, < 5.10.239", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["5.15.186"], "affected": ">= 5.11, < 5.15.186", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.1.142"], "affected": ">= 5.16, < 6.1.142", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.6.94"], "affected": ">= 6.2, < 6.6.94", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.12.34"], "affected": ">= 6.7, < 6.12.34", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": ["6.15.3"], "affected": ">= 6.13, < 6.15.3", "ecosystem": "vendor"}, {"name": "linux kernel", "fixed": [], "affected": "= 6.16", "ecosystem": "vendor"}, {"name": "debian linux", "fixed": [], "affected": "= 11.0", "ecosystem": "vendor"}, {"name": "Linux Kernel", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["exploited", "infrastructure", "kubernetes", "linux", "self-hosted"]
not_affected_if: ["unknown"]
published_at: "2025-07-22T08:15:23+00:00"
first_seen_at: "2026-10-23T19:11:51+00:00"
updated_at: "2026-10-24T00:09:50+00:00"
sources: [{"source": "kev", "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2025-38352", "first_seen_at": "2026-10-23T19:11:51+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38352", "first_seen_at": "2026-10-23T22:29:05+00:00"}]
---

# In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between…

A 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, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:linux kernel affected >= 2.6.36, < 5.4.295 fixed 5.4.295
- vendor:linux kernel affected >= 5.5, < 5.10.239 fixed 5.10.239
- vendor:linux kernel affected >= 5.11, < 5.15.186 fixed 5.15.186
- vendor:linux kernel affected >= 5.16, < 6.1.142 fixed 6.1.142
- vendor:linux kernel affected >= 6.2, < 6.6.94 fixed 6.6.94
- vendor:linux kernel affected >= 6.7, < 6.12.34 fixed 6.12.34
- vendor:linux kernel affected >= 6.13, < 6.15.3 fixed 6.15.3
- vendor:linux kernel affected = 6.16 fixed ?
- vendor:debian linux affected = 11.0 fixed ?
- vendor:Linux Kernel affected ? fixed ?

## Fix

Apply the kernel vendor's mitigation or patch per CISA guidance; discontinue use of the product if no mitigation is available.

## Timeline

- 2026-10-23T19:11:51+00:00 kev https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2025-38352
- 2026-10-23T22:29:05+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-38352

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_