CVE-2025-39944

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-04. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-32396 (ENISA EUVD) · GHSA-63mr-vmpc-c5r9 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp()

The original code relies on cancel_delayed_work() in otx2_ptp_destroy(), which does not ensure that the delayed work item synctstamp_work has fully completed if it was already running. This leads to use-after-free scenarios where otx2_ptp is deallocated by otx2_ptp_destroy(), while synctstamp_work remains active and attempts to dereference otx2_ptp in otx2_sync_tstamp(). Furthermore, the synctstamp_work is cyclic, the likelihood of triggering the bug is nonnegligible.

A typical race condition is illustrated below:

CPU 0 (cleanup) | CPU 1 (delayed work callback) otx2_remove() | otx2_ptp_destroy() | otx2_sync_tstamp() cancel_delayed_work() | kfree(ptp) | | ptp = container_of(...); //UAF | ptp-> //UAF

This is confirmed by a KASAN report:

BUG: KASAN: slab-use-after-free in __run_timer_base.part.0+0x7d7/0x8c0 Write of size 8 at addr ffff88800aa09a18 by task bash/136 ... Call Trace: dump_stack_lvl+0x55/0x70 print_report+0xcf/0x610 ? __run_timer_base.part.0+0x7d7/0x8c0 kasan_report+0xb8/0xf0 ? __run_timer_base.part.0+0x7d7/0x8c0 __run_timer_base.part.0+0x7d7/0x8c0 ? __pfx___run_timer_base.part.0+0x10/0x10 ? __pfx_read_tsc+0x10/0x10 ? ktime_get+0x60/0x140 ? lapic_next_event+0x11/0x20 ? clockevents_program_event+0x1d4/0x2a0 run_timer_softirq+0xd1/0x190 handle_softirqs+0x16a/0x550 irq_exit_rcu+0xaf/0xe0 sysvec_apic_timer_interrupt+0x70/0x80 ... Allocated by task 1: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7f/0x90 otx2_ptp_init+0xb1/0x860 otx2_probe+0x4eb/0xc30 local_pci_probe+0xdc/0x190 pci_device_probe+0x2fe/0x470 really_probe+0x1ca/0x5c0 __driver_probe_device+0x248/0x310 driver_probe_device+0x44/0x120 __driver_attach+0xd2/0x310 bus_for_each_dev+0xed/0x170 bus_add_driver+0x208/0x500 driver_register+0x132/0x460 do_one_initcall+0x89/0x300 kernel_init_freeable+0x40d/0x720 kernel_init+0x1a/0x150 ret_from_fork+0x10c/0x1a0 ret_from_fork_asm+0x1a/0x30

Freed by task 136: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3a/0x60 __kasan_slab_free+0x3f/0x50 kfree+0x137/0x370 otx2_ptp_destroy+0x38/0x80 otx2_remove+0x10d/0x4c0 pci_device_remove+0xa6/0x1d0 device_release_driver_internal+0xf8/0x210 pci_stop_bus_device+0x105/0x150 pci_stop_and_remove_bus_device_locked+0x15/0x30 remove_store+0xcc/0xe0 kernfs_fop_write_iter+0x2c3/0x440 vfs_write+0x871/0xd70 ksys_write+0xee/0x1c0 do_syscall_64+0xac/0x280 entry_SYSCALL_64_after_hwframe+0x77/0x7f ...

Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the delayed work item is properly canceled before the otx2_ptp is deallocated.

This bug was initially identified through static analysis. To reproduce and test it, I simulated the OcteonTX2 PCI device in QEMU and introduced artificial delays within the otx2_sync_tstamp() function to increase the likelihood of triggering the bug.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 4, 2025

Last Modified

October 19, 2026

Advisory Details (5)

Auto-updated Jul 30, 2026
Patch available.
Web page

octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ff27e23b311fed4d25e3852e27ba693416d4c7b3
Web page

octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8b4687151021db61841af983f1cb7be6915d4ef
Web page

octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2cfefa14ce8137b17f99683f968bebf134b6a48
Web page

octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ca20bb7b4bde72110c3ae78423cbfdd0157aa36
Web page

octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2786879aebf363806a13d41e8d5f99202ddd23d9

Vendor Advisories for CVE-2025-39944(1)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-10-27ubuntu
linuxKernel @ 6.1.154 (fixes >=6.1.0)—osv

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.153-1~deb11u1 (12 versions)
  • every version up to 6.1.158-1~deb11u1: fixed in 6.1.158-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (44 versions)
  • every version up to 6.1.158-1: fixed in 6.1.158-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.57-1~bpo12+1 (6 versions)
  • every version up to 6.12.57-1: fixed in 6.12.57-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (67 versions)
  • every version up to 6.16.9-1: fixed in 6.16.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

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 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 232 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-27 18:31 UTCEG score recompute
  7. 2026-10-27 18:31 UTCVendor advisory
  8. 2026-10-27 18:30 UTCGHSA enrichmentGHSA-63mr-vmpc-c5r9 · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-25 16:28 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-19 21:28 UTCEG score recompute
  19. 2026-10-19 21:28 UTCVendor advisory
  20. 2026-10-19 21:28 UTCGHSA enrichmentGHSA-63mr-vmpc-c5r9 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-18 05:35 UTCEG score recompute
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 73 more
  1. 2026-10-15 22:50 UTCGHSA enrichmentGHSA-63mr-vmpc-c5r9 · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-15 22:11 UTCEG score recompute
  3. 2026-10-15 22:11 UTCGHSA enrichmentGHSA-63mr-vmpc-c5r9 · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-12 17:06 UTCEG score recompute
  8. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-11 20:39 UTCEG score recompute
  10. 2026-10-11 18:50 UTCEG score recompute
  11. 2026-10-11 15:27 UTCEG score recompute
  12. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-09-27 02:15 UTCOSV refresh
  25. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  26. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  27. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  28. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  29. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  30. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  31. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  32. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  33. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  34. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  35. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  36. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  37. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  38. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  40. 2026-09-07 11:18 UTCOSV refresh
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  44. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  48. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  51. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-08-20 20:31 UTCOSV refresh
  56. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  66. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  68. 2026-08-05 12:55 UTCEG score recompute
  69. 2026-08-05 12:55 UTCVendor advisory
  70. 2026-08-05 12:55 UTCGHSA enrichmentGHSA-63mr-vmpc-c5r9 · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  72. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  73. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-39944?
CVE-2025-39944 is a high-severity vulnerability; its CVE record was published on October 4, 2025. In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() The original code relies on cancel_delayed_work() in otx2_ptp_destroy(), which does not ensure that the delayed work item synctstamp_work has fully completed if it was…
When was the CVE record for CVE-2025-39944 published?
The CVE record for CVE-2025-39944 was published on October 4, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-39944 actively exploited?
CVE-2025-39944 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39944?
CVE-2025-39944 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-39944?
A fix for CVE-2025-39944 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39944 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-39944

Explore →

Is Your Infrastructure Affected by CVE-2025-39944?

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

Book a Demo →Browse All CVEs