Log in / Sign up

Vulnerability details

CVE-2025-38352

Actively exploited
Linux Linux

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

CVSS 3.1
7.8High

Remedy

Required action (CISA): Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (due: 2025-09-25)

Versions not listed as affected in the CVE record:
  • Linux — version 78a4b8e3795b31dae58762bc091bb0f4f74a2200 and later
  • Linux — version c076635b3a42771ace7d276de8dc3bc76ee2ba1b and later
  • Linux — version 2f3daa04a9328220de46f0d5c919a6c0073a9f0b and later
  • Linux — version 764a7a5dfda23f69919441f2eac2a83e7db6e5bb and later
  • Linux — version 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff and later
  • Linux — version c29d5318708e67ac13c1b6fc1007d179fb65b4d7 and later

Official description

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 scores

ScoreVersionSourceVector
7.8High 3.1 CVEProject cvelistV5 (CNA) (Linux) CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersionsSource
Linux Linux 2.6.36 CVEProject cvelistV5 (CNA)
Linux Linux 0bdd2ed4138ec04e09b4f8165981efc99e439f55 ≤ v < c076635b3a42771ace7d276de8dc3bc76ee2ba1b CVEProject cvelistV5 (CNA)
Linux Linux 0bdd2ed4138ec04e09b4f8165981efc99e439f55 ≤ v < 2f3daa04a9328220de46f0d5c919a6c0073a9f0b CVEProject cvelistV5 (CNA)
Linux Linux 0bdd2ed4138ec04e09b4f8165981efc99e439f55 ≤ v < 764a7a5dfda23f69919441f2eac2a83e7db6e5bb CVEProject cvelistV5 (CNA)
Linux Linux 0bdd2ed4138ec04e09b4f8165981efc99e439f55 ≤ v < 78a4b8e3795b31dae58762bc091bb0f4f74a2200 CVEProject cvelistV5 (CNA)
Linux Linux 0bdd2ed4138ec04e09b4f8165981efc99e439f55 ≤ v < c29d5318708e67ac13c1b6fc1007d179fb65b4d7 CVEProject cvelistV5 (CNA)
Linux Linux 0bdd2ed4138ec04e09b4f8165981efc99e439f55 ≤ v < 460188bc042a3f40f72d34b9f7fc6ee66b0b757b CVEProject cvelistV5 (CNA)
Linux Linux 0bdd2ed4138ec04e09b4f8165981efc99e439f55 ≤ v < f90fff1e152dedf52b932240ebbd670d83330eca CVEProject cvelistV5 (CNA)
Linux Linux 0bdd2ed4138ec04e09b4f8165981efc99e439f55 ≤ v < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff CVEProject cvelistV5 (CNA)

References and advisories

12
Kolun on Telegram @kolunsec Exploited CVEs, key news and a daily digest Alerts for this product's next CVEsFollow the product to get new vulnerabilities on Telegram.

Details

Published
2025-07-22
Last updated
2026-09-08
State
Published
Assigner (CNA)
Linux
Kolun priority
90 · Critical

CISA KEV catalog

Date added
2025-09-04
Due date
2025-09-25
Used in ransomware
Unknown

Exploit prediction (EPSS)

1.35%
Probability of exploitation in 30 days
72%
Percentile (among all CVEs)

SSVC assessment (CISA)

Automatable
No
Exploitation
Active
Technical impact
Total

Weaknesses (CWE)

  • CWE-367
    Time-of-check Time-of-use (TOCTOU) Race Condition