Skip to main content
ExploitedIn CISA KEVFix available

CVE-2025-38352

Exploitation confirmed. First attested on 2025-09-04 by CISA-ADP, CISA KEV, GCVE · kevintel.

  • Published2025-07-22
  • Fixed in6.15.3 · 6.12.34 · 6.6.94 · 6.1.142 · 5.15.186 · 5.10.239
  • WeaknessCWE-367

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2025-07-2208:15CVE publishedNVD
  2. 2025-09-04Added to the CISA KEV catalogCISA KEV
  3. 2025-09-04Listed as exploited by GCVEGCVE
  4. 2025-09-04Exploitation first reportedCISA KEV
  5. 2025-09-0503:55SSVC exploitation set to activeCISA-ADP

Versions per branch

NVD · OSV
Linux linux kernel
BranchAffectedFixed in
6.x≥ 6.13, < 6.15.36.15.3
6.x≥ 6.13.0, < 6.15.36.15.3
6.x≥ 6.7, < 6.12.346.12.34
6.x≥ 6.7.0, < 6.12.346.12.34
6.x≥ 6.2, < 6.6.946.6.94
6.x≥ 6.2.0, < 6.6.946.6.94
6.1≥ 5.16, < 6.1.1426.1.142
6.1≥ 5.16.0, < 6.1.1426.1.142
5.x≥ 5.11, < 5.15.1865.15.186
5.x≥ 5.11.0, < 5.15.1865.15.186
5.x≥ 5.5, < 5.10.2395.10.239
5.x≥ 5.5.0, < 5.10.2395.10.239
Debian debian linux
BranchAffectedFixed in
11.0= 11.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 78a4b8e3795b31dae58762bc091bb0f4f74a2200fixed in 78a4b8e3795b31dae58762bc091bb0f4f74a2200git
    • ≥ 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < c076635b3a42771ace7d276de8dc3bc76ee2ba1bfixed in c076635b3a42771ace7d276de8dc3bc76ee2ba1bgit
    • ≥ 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 2f3daa04a9328220de46f0d5c919a6c0073a9f0bfixed in 2f3daa04a9328220de46f0d5c919a6c0073a9f0bgit
    • ≥ 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 764a7a5dfda23f69919441f2eac2a83e7db6e5bbfixed in 764a7a5dfda23f69919441f2eac2a83e7db6e5bbgit
    • ≥ 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106fffixed in 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ffgit
    • ≥ 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < c29d5318708e67ac13c1b6fc1007d179fb65b4d7fixed in c29d5318708e67ac13c1b6fc1007d179fb65b4d7git
    • ≥ 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 460188bc042a3f40f72d34b9f7fc6ee66b0b757bfixed in 460188bc042a3f40f72d34b9f7fc6ee66b0b757bgit
    • ≥ 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < f90fff1e152dedf52b932240ebbd670d83330ecafixed in f90fff1e152dedf52b932240ebbd670d83330ecagit
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 2.6.36no fix stated

    Not affected < 2.6.36 · ≥ 5.4.295, ≤ 5.4.* · ≥ 5.10.239, ≤ 5.10.* · ≥ 5.15.186, ≤ 5.15.* · ≥ 6.1.142, ≤ 6.1.* · ≥ 6.6.94, ≤ 6.6.* · ≥ 6.12.34, ≤ 6.12.*

    2 more version lines in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-08-05

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • :linux_kernel:Androidfrom :0 · fixed in :2025-09-05
  • bpftoolTuxCare:AlmaLinux:9.2all versions · fixed in 7.0.0-284.1101.el9_2.tuxcare.7.els19
  • dtb-aarch64openSUSE:Leap 15.6all versions · fixed in 6.4.0-150600.23.65.1and 10 other packages
  • kernelTuxCare:RHEL:7all versions · fixed in 3.10.0-1160.136.1.el7.tuxcare.els24and 10 other packages
  • kernelTuxCare:OracleLinux:7all versions · fixed in 3.10.0-1160.119.1.0.5.el7.tuxcare.els24and 10 other packages
  • kernelTuxCare:OracleLinux:6all versions · fixed in 2.6.32-754.35.8.el6.tuxcare.els25and 9 other packages
  • kernelTuxCare:CentOS:8.5all versions · fixed in 4.18.0-348.7.1.el8_5.tuxcare.els31and 21 other packages
  • kernelTuxCare:CentOS:8.4all versions · fixed in 4.18.0-305.25.1.el8_4.tuxcare.els31and 21 other packages

196 more package ranges on OSV.dev

Vendor advisories

  • CVE-2025-38352 Red Hat Product Security1,985 products fixed

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

  • RHSA-2025:16045 Red Hat Product Security35 products fixed

    Red Hat Security Advisory: kpatch-patch-4_18_0-372_118_1, kpatch-patch-4_18_0-372_131_1, kpatch-patch-4_18_0-372_137_1, kpatch-patch-4_18_0-372_145_1, and kpatch-patch-4_18_0-372_158_1 security update

  • RHSA-2025:16008 Red Hat Product Security35 products fixed

    Red Hat Security Advisory: kpatch-patch-4_18_0-477_107_1, kpatch-patch-4_18_0-477_67_1, kpatch-patch-4_18_0-477_81_1, kpatch-patch-4_18_0-477_89_1, and kpatch-patch-4_18_0-477_97_1 security update

  • RHSA-2025:15932 Red Hat Product Security35 products fixed

    Red Hat Security Advisory: kpatch-patch-5_14_0-427_31_1, kpatch-patch-5_14_0-427_44_1, kpatch-patch-5_14_0-427_55_1, kpatch-patch-5_14_0-427_68_2, and kpatch-patch-5_14_0-427_84_1 security update

  • RHSA-2025:15933 Red Hat Product Security35 products fixed

    Red Hat Security Advisory: kpatch-patch-5_14_0-70_112_1, kpatch-patch-5_14_0-70_121_1, kpatch-patch-5_14_0-70_124_1, kpatch-patch-5_14_0-70_132_1, and kpatch-patch-5_14_0-70_144_1 security update

  • RHSA-2025:15931 Red Hat Product Security35 products fixed

    Red Hat Security Advisory: kpatch-patch-5_14_0-284_104_1, kpatch-patch-5_14_0-284_117_1, kpatch-patch-5_14_0-284_134_1, kpatch-patch-5_14_0-284_79_1, and kpatch-patch-5_14_0-284_92_1 security update

17 more advisories

Full record on NVD

Fix

  1. Update Linux linux kernel to 6.15.3 · 6.12.34 · 6.6.94 · 6.1.142 · 5.15.186 · 5.10.239
  2. CISA’s 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 2025-09-25
  3. Vendor fix Red Hat Product Security RHSA-2025:16045 · 35 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
  4. Workaround from the vendor Red Hat Product Security RHSA-2025:16045 · 35 productsMitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

CISA Known Exploited Vulnerability

Date Added
2025-09-04
Patch Due Date
2025-09-25
Ransomware Use
Unknown
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.

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2025-07-22
Last Modified
2026-09-08
NVD status
Analyzed
GitHub Advisory
GHSA-mr4j-mh66-4679

Frequently asked questions

What is CVE-2025-38352?

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.

Is CVE-2025-38352 actively exploited?

Yes. CVE-2025-38352 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2025-09-25.

What is the CVSS score for CVE-2025-38352?

CVE-2025-38352 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record