SECUFOCUSNOW
Home›CVE index›CVE-2025-38352
CISA KEV · Known exploitedHigh

CVE-2025-38352

Linux Linux, linux kernel, debian linux

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 fi...

CVSS
7.8
EPSS
1.25%
66.5% percentile
CISA KEV
Listed
Published
2025.07.22
PRIORITY ASSESSMENT

Immediate review

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog.

Known exploitationConfirmed by CISA KEV
Exploit probability1.25%
Technical severityCVSS 7.8

Vulnerability overview

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 fi...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 78a4b8e3795b31dae58762bc091bb0f4f74a2200, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < c076635b3a42771ace7d276de8dc3bc76ee2ba1b, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 2f3daa04a9328220de46f0d5c919a6c0073a9f0b, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 764a7a5dfda23f69919441f2eac2a83e7db6e5bb, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < c29d5318708e67ac13c1b6fc1007d179fb65b4d7, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 460188bc042a3f40f72d34b9f7fc6ee66b0b757b, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < f90fff1e152dedf52b932240ebbd670d83330eca, >= 2.6.36, >= 2.6.36 < 5.4.295, >= 5.5 < 5.10.239, >= 5.11 < 5.15.186, >= 5.16 < 6.1.142, >= 6.2 < 6.6.94, >= 6.7 < 6.12.34, >= 6.13 < 6.15.3, 6.16, 11.0
Fixed versions
5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.34, 6.15.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
CISA required action

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 date: 2025.09.25
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-367
KEV added
2025.09.04
Ransomware use
미확인
CVE-2025-38352 — Linux Linux, linux kernel, debian linux | SECUFOCUS NOW