CVE-2025-38352

HIGHNVD 7.49.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-09-04), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.4 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
7.4
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 1%CVSS: 7.4Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
7.4
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
68.4%
KEV
⚠ Exploited

Published

July 22, 2025

Last Modified

January 8, 2026

Advisory Details (10)

Auto-updated Jun 6, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
generic Patch Available

[SECURITY] [DLA 4327-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
generic

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f90fff1e152dedf52b932240ebbd670d83330eca
generic

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c29d5318708e67ac13c1b6fc1007d179fb65b4d7
generic

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c076635b3a42771ace7d276de8dc3bc76ee2ba1b
generic

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78a4b8e3795b31dae58762bc091bb0f4f74a2200
generic

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/764a7a5dfda23f69919441f2eac2a83e7db6e5bb
generic

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/460188bc042a3f40f72d34b9f7fc6ee66b0b757b
generic

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f3daa04a9328220de46f0d5c919a6c0073a9f0b
generic

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff

Vendor Advisories for CVE-2025-38352(14)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1044.50+fips1) @ noble2026-07-22ubuntu
ubuntulinux-tools-azure-fips-5.4 (5.4.0.1157.94) @ focal2026-07-22ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1096.94) @ jammy2026-07-22ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1029.32) @ noble2026-07-22ubuntu
ubuntulinux-tools-fips (4.4.0.1119.120) @ xenial2026-07-22ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1012.12~24.04.1) @ noble2026-07-22ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1090.96~20.04.1) @ focal2026-07-22ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1014.14) @ plucky2026-07-22ubuntu
redhatkpatch-patch2025-09-17redhat
redhatkernel-0:5.14.0-427.88.1.el9_42025-09-11redhat
redhatkernel-0:4.18.0-305.172.1.el8_42025-09-11redhat
redhatkernel-0:5.14.0-284.137.1.el9_22025-09-11redhat
redhatkernel-0:5.14.0-570.42.2.el9_62025-09-11redhat
redhatkernel-0:6.12.0-55.32.1.el10_02025-09-11redhat
redhatkernel-0:5.14.0-70.146.1.el9_02025-09-11redhat
redhatkernel-rt-0:3.10.0-1160.139.1.rt56.1291.el72025-09-10redhat
redhatkernel-0:4.18.0-477.110.1.el8_82025-09-10redhat
redhatkernel-0:3.10.0-1160.139.1.el72025-09-10redhat
redhatkernel-0:4.18.0-193.168.1.el8_22025-09-10redhat
redhatkernel-0:4.18.0-372.160.1.el8_62025-09-10redhat
redhatkernel-rt-0:5.14.0-284.137.1.rt14.422.el9_22025-09-10redhat
redhatkernel-rt-0:5.14.0-70.146.1.rt21.218.el9_02025-09-10redhat
redhatkernel-rt-0:4.18.0-553.74.1.rt7.415.el8_102025-09-08redhat
redhatkernel-0:4.18.0-553.74.1.el8_102025-09-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 96× in last 7d / 396× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 696 total refreshes for this CVE.

  1. 2026-07-23 02:54 UTCEG score recompute
  2. 2026-07-22 22:10 UTCEG score recompute
  3. 2026-07-22 22:10 UTCVendor advisory
  4. 2026-07-22 22:09 UTCGHSA enrichment
  5. 2026-07-22 19:40 UTCCISA KEV update
  6. 2026-07-22 17:48 UTCEG score recompute
  7. 2026-07-22 17:48 UTCVendor advisory
  8. 2026-07-22 17:48 UTCGHSA enrichment
  9. 2026-07-22 14:07 UTCEPSS rescore
  10. 2026-07-22 14:07 UTCEPSS rescore
  11. 2026-07-22 13:27 UTCVendor advisory
  12. 2026-07-22 13:27 UTCGHSA enrichment
  13. 2026-07-22 09:06 UTCVendor advisory
  14. 2026-07-22 09:06 UTCGHSA enrichment
  15. 2026-07-22 04:44 UTCVendor advisory
  16. 2026-07-22 04:44 UTCGHSA enrichment
  17. 2026-07-22 00:23 UTCVendor advisory
  18. 2026-07-22 00:22 UTCGHSA enrichment
  19. 2026-07-21 20:02 UTCVendor advisory
  20. 2026-07-21 20:01 UTCGHSA enrichment
  21. 2026-07-21 15:40 UTCEG score recompute
  22. 2026-07-21 15:40 UTCVendor advisory
  23. 2026-07-21 15:39 UTCGHSA enrichment
  24. 2026-07-21 15:24 UTCEPSS rescore
  25. 2026-07-21 14:37 UTCCISA KEV update
Show 75 more
  1. 2026-07-21 11:18 UTCVendor advisory
  2. 2026-07-21 11:17 UTCGHSA enrichment
  3. 2026-07-21 06:55 UTCVendor advisory
  4. 2026-07-21 06:55 UTCGHSA enrichment
  5. 2026-07-21 02:34 UTCVendor advisory
  6. 2026-07-21 02:33 UTCGHSA enrichment
  7. 2026-07-20 22:13 UTCVendor advisory
  8. 2026-07-20 22:12 UTCGHSA enrichment
  9. 2026-07-20 17:51 UTCEG score recompute
  10. 2026-07-20 17:51 UTCVendor advisory
  11. 2026-07-20 17:50 UTCGHSA enrichment
  12. 2026-07-20 17:07 UTCEPSS rescore
  13. 2026-07-20 13:30 UTCVendor advisory
  14. 2026-07-20 13:29 UTCGHSA enrichment
  15. 2026-07-20 09:08 UTCVendor advisory
  16. 2026-07-20 09:07 UTCGHSA enrichment
  17. 2026-07-20 04:47 UTCVendor advisory
  18. 2026-07-20 04:47 UTCGHSA enrichment
  19. 2026-07-20 00:26 UTCVendor advisory
  20. 2026-07-19 20:05 UTCVendor advisory
  21. 2026-07-19 20:04 UTCGHSA enrichment
  22. 2026-07-19 15:43 UTCEG score recompute
  23. 2026-07-19 15:43 UTCVendor advisory
  24. 2026-07-19 15:42 UTCGHSA enrichment
  25. 2026-07-19 14:30 UTCEPSS rescore
  26. 2026-07-19 14:30 UTCEPSS rescore
  27. 2026-07-19 11:21 UTCVendor advisory
  28. 2026-07-19 11:21 UTCGHSA enrichment
  29. 2026-07-19 06:59 UTCVendor advisory
  30. 2026-07-19 06:59 UTCGHSA enrichment
  31. 2026-07-19 02:38 UTCEG score recompute
  32. 2026-07-19 02:38 UTCVendor advisory
  33. 2026-07-19 02:38 UTCGHSA enrichment
  34. 2026-07-19 02:28 UTCEPSS rescore
  35. 2026-07-19 02:28 UTCEPSS rescore
  36. 2026-07-18 22:17 UTCVendor advisory
  37. 2026-07-18 22:16 UTCGHSA enrichment
  38. 2026-07-18 17:55 UTCVendor advisory
  39. 2026-07-18 17:55 UTCGHSA enrichment
  40. 2026-07-18 13:34 UTCEG score recompute
  41. 2026-07-18 13:34 UTCVendor advisory
  42. 2026-07-18 13:34 UTCGHSA enrichment
  43. 2026-07-18 10:04 UTCEPSS rescore
  44. 2026-07-18 10:04 UTCEPSS rescore
  45. 2026-07-18 09:12 UTCVendor advisory
  46. 2026-07-18 09:12 UTCGHSA enrichment
  47. 2026-07-18 04:51 UTCVendor advisory
  48. 2026-07-18 04:51 UTCGHSA enrichment
  49. 2026-07-18 00:29 UTCVendor advisory
  50. 2026-07-18 00:29 UTCGHSA enrichment
  51. 2026-07-17 20:08 UTCVendor advisory
  52. 2026-07-17 20:08 UTCGHSA enrichment
  53. 2026-07-17 15:47 UTCVendor advisory
  54. 2026-07-17 15:47 UTCGHSA enrichment
  55. 2026-07-17 11:26 UTCVendor advisory
  56. 2026-07-17 11:26 UTCGHSA enrichment
  57. 2026-07-17 07:05 UTCEG score recompute
  58. 2026-07-17 07:05 UTCVendor advisory
  59. 2026-07-17 07:05 UTCGHSA enrichment
  60. 2026-07-17 02:44 UTCVendor advisory
  61. 2026-07-17 02:44 UTCGHSA enrichment
  62. 2026-07-16 22:23 UTCVendor advisory
  63. 2026-07-16 22:23 UTCGHSA enrichment
  64. 2026-07-16 18:03 UTCVendor advisory
  65. 2026-07-16 18:02 UTCGHSA enrichment
  66. 2026-07-16 17:04 UTCCISA KEV update
  67. 2026-07-16 17:02 UTCEPSS rescore
  68. 2026-07-16 13:41 UTCVendor advisory
  69. 2026-07-16 13:41 UTCGHSA enrichment
  70. 2026-07-16 09:20 UTCVendor advisory
  71. 2026-07-16 09:20 UTCGHSA enrichment
  72. 2026-07-16 04:58 UTCVendor advisory
  73. 2026-07-16 04:58 UTCGHSA enrichment
  74. 2026-07-16 00:37 UTCVendor advisory
  75. 2026-07-16 00:37 UTCGHSA enrichment

Publicly available exploits

(4 references)

Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCAnalyticETH/chronomaly-webos
    First seen May 30, 2026

    CVE-2025-38352 kernel exploit for LG webOS Smart TVs (ARM64). Achieves persistent root on real consumer hardware with novel exploitation techniques. Responsibly disclosed to LG.

    Open source ↗
  • GitHub PoCjordelmir/Elysium-Vanguard-Sentinel-Audit
    First seen Feb 24, 2026

    The official Sentinel Edition v7.11 - Hypervisor Detection & Kernel Memory Audit Suite for Honor Magic V2. Investigating CVE-2025-38352 and EL2 RKP defenses.

    Open source ↗
  • GitHub PoCfarazsth98/chronomaly
    First seen Jan 3, 2026

    Android kernel exploit for CVE-2025-38352, previously exploited in-the-wild. Targets vulnerable x86_64 Linux kernels v5.10.x.

    Open source ↗
  • GitHub PoCfarazsth98/poc-CVE-2025-38352
    First seen Dec 21, 2025

    This is a proof of concept for CVE-2025-38352, a vulnerability in the Linux kernel's POSIX CPU timers implementation. The September 2025 Android Bulletin mentions that this vulnerability has been used in limited, targeted exploitation in the wild.

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2025-38352?
CVE-2025-38352 is a high vulnerability published on July 22, 2025. In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handleposixcputimers() and posixcputimerdel() If an exiting non-autoreaping task has already passed exit_notify() and calls handleposixcpu_timers() from IRQ, it can be reaped by its parent or…
When was CVE-2025-38352 disclosed?
CVE-2025-38352 was first published in the National Vulnerability Database on July 22, 2025, with the most recent update on January 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38352 actively exploited?
Yes. CISA added CVE-2025-38352 to the Known Exploited Vulnerabilities catalog on September 4, 2025, affecting Linux Kernel. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2025-38352?
CVE-2025-38352 has a CVSS v3 base score of 7.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2025-38352?
CVE-2025-38352 affects Linux Kernel. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2025-38352?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38352, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-38352

Explore →

Is Your Infrastructure Affected by CVE-2025-38352?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs