Skip to content
vulnerability

CVE-2025-38352

7.8
High
KEV · Exploited in wildEPSS 1%Patch available

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.

exploited
Yes, in CISA KEV since 4 Sept 2025fix by 25 Sept 2025 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Fixed in < 2.6.36, >= 5.4.295 and <= 5.4.*, >= 5.10.239 and <= 5.10.* +6
likelihood
EPSS 1.4%
Published 22 Jul 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstUpgrade to a fixed release: < 2.6.36, >= 5.4.295 and <= 5.4.*, >= 5.10.239 and <= 5.10.*, >= 5.15.186 and <= 5.15.* (+5 more below).

triage
surface unknownruntimeWAF can block: noAV · localCWE-367· Common Weakness

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2025-38352 being exploited?

Yes. CVE-2025-38352 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-38352?

CVE-2025-38352 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-38352?

Yes. A fix has been recorded for CVE-2025-38352. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-38352 affect?

CVE-2025-38352 affects linux:linux_kernel, debian:debian_linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
linux:linux_kerneldebian:debian_linux
affected versions
Linux
  • affected>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 78a4b8e3795b31dae58762bc091bb0f4f74a2200
  • affected>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < c076635b3a42771ace7d276de8dc3bc76ee2ba1b
  • affected>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 2f3daa04a9328220de46f0d5c919a6c0073a9f0b
  • affected>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 764a7a5dfda23f69919441f2eac2a83e7db6e5bb
  • affected>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff
  • affected>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < c29d5318708e67ac13c1b6fc1007d179fb65b4d7
  • affected>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < 460188bc042a3f40f72d34b9f7fc6ee66b0b757b
  • affected>= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 and < f90fff1e152dedf52b932240ebbd670d83330eca
  • affected2.6.36
vendor says fixed in< 2.6.36, >= 5.4.295 and <= 5.4.*, >= 5.10.239 and <= 5.10.*, >= 5.15.186 and <= 5.15.*, >= 6.1.142 and <= 6.1.*, >= 6.6.94 and <= 6.6.*, >= 6.12.34 and <= 6.12.*, >= 6.15.3 and <= 6.15.*, >= 6.16 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 6 GitHub proofs of concept

GitHub proofs of concept
+2 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 5 Sept 2025 (SSVC 2.0.3).

timeline

  1. 22 Jul 2025Published
  2. 4 Sept 2025Added to CISA KEV (exploited in the wild) · 44 days later
  3. 5 Sept 2025CISA SSVC assessment: exploitation active · 1 day later
  4. 25 Sept 2025CISA remediation due date (US federal agencies) · 20 days later
  5. 21 Dec 2025First proof-of-concept repository on GitHub (unvetted) · 87 days (about 3 months) later
  6. 8 Sept 2026CVE record last updated · 262 days (about 9 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 55 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
12 references in the CVE record: 1 exploit, 11 links
Show 4 more
  • Linkgit.kernel.org /stable/c/f90fff1e152dedf52b932240ebbd670d83330eca
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-38352
  • Linklists.debian.org /debian-lts-announce/2025/10/msg00008.html
  • Linklists.debian.org /debian-lts-announce/2025/10/msg00007.html

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved