CVE-2026-23025

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 2026-01-31. 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 — 3 sources updated this week

Also known asEUVD-2026-5069 (ENISA EUVD) · GHSA-c784-4r38-57xw (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:

mm/page_alloc: prevent pcp corruption with SMP=n

The kernel test robot has reported:

BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28 lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0 CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT 8cc09ef94dcec767faa911515ce9e609c45db470 Call Trace: __dump_stack (lib/dump_stack.c:95) dump_stack_lvl (lib/dump_stack.c:123) dump_stack (lib/dump_stack.c:130) spin_dump (kernel/locking/spinlock_debug.c:71) do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?) _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138) __free_frozen_pages (mm/page_alloc.c:2973) ___free_pages (mm/page_alloc.c:5295) __free_pages (mm/page_alloc.c:5334) tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290) ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289) ? rcu_core (kernel/rcu/tree.c:?) rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861) rcu_core_si (kernel/rcu/tree.c:2879) handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623) __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725) irq_exit_rcu (kernel/softirq.c:741) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052) RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194) free_pcppages_bulk (mm/page_alloc.c:1494) drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632) __drain_all_pages (mm/page_alloc.c:2731) drain_all_pages (mm/page_alloc.c:2747) kcompactd (mm/compaction.c:3115) kthread (kernel/kthread.c:465) ? __cfi_kcompactd (mm/compaction.c:3166) ? __cfi_kthread (kernel/kthread.c:412) ret_from_fork (arch/x86/kernel/process.c:164) ? __cfi_kthread (kernel/kthread.c:412) ret_from_fork_asm (arch/x86/entry/entry_64.S:255)

Matthew has analyzed the report and identified that in drain_page_zone() we are in a section protected by spin_lock(&pcp->lock) and then get an interrupt that attempts spin_trylock() on the same lock. The code is designed to work this way without disabling IRQs and occasionally fail the trylock with a fallback. However, the SMP=n spinlock implementation assumes spin_trylock() will always succeed, and thus it's normally a no-op. Here the enabled lock debugging catches the problem, but otherwise it could cause a corruption of the pcp structure.

The problem has been introduced by commit 574907741599 ("mm/page_alloc: leave IRQs enabled for per-cpu page allocations"). The pcp locking scheme recognizes the need for disabling IRQs to prevent nesting spin_trylock() sections on SMP=n, but the need to prevent the nesting in spin_lock() has not been recognized. Fix it by introducing local wrappers that change the spin_lock() to spin_lock_iqsave() with SMP=n and use them in all places that do spin_lock(&pcp->lock).

[[email protected]: add pcp_ prefix to the spin_lock_irqsave wrappers, per Steven]

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.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
10th
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 (model v2026.06.15, score date 2026-11-05). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

January 31, 2026

Last Modified

November 5, 2026

Advisory Details (6)

Auto-updated Jun 6, 2026
Patch available.
Web page

SSA-253495

https://cert-portal.siemens.com/productcert/html/ssa-253495.html
Web page

mm/page_alloc: prevent pcp corruption with SMP=n - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/page_alloc: prevent pcp corruption with SMP=n - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68688fc4eab007834b4c2d740214423ba2a335a8
Web page

mm/page_alloc: prevent pcp corruption with SMP=n - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a04ff9cd816e7346fcc8126f00ed80481f6569d
Web page

mm/page_alloc: prevent pcp corruption with SMP=n - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3098f8f7c7b0686c74827aec42a2c45e69801ff8
Web page

mm/page_alloc: prevent pcp corruption with SMP=n - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/038a102535eb49e10e93eafac54352fcc5d78847

Vendor Advisories for CVE-2026-23025(1)

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

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1018.20~24.04.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-10-24ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-10-24ubuntu
ubuntulowlatency-4.4 (4.4.0-243) @ xenial2026-10-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-24ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1030.30) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1031.31) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1019.19~24.04.3+1) @ noble2026-10-24ubuntu
linuxKernel @ 6.1.162 (fixes >=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.159-1~deb11u1 (14 versions)
  • every version up to 6.1.162-1~deb11u1: fixed in 6.1.162-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (97 versions)
  • every version up to 6.18.8-1: fixed in 6.18.8-1
—

All Vendor Advisories

(16)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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 99 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-23025?
CVE-2026-23025 is a high-severity vulnerability; its CVE record was published on January 31, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: prevent pcp corruption with SMP=n The kernel test robot has reported: BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28 lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0 CPU:…
When was the CVE record for CVE-2026-23025 published?
The CVE record for CVE-2026-23025 was published on January 31, 2026. 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 November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-23025 actively exploited?
CVE-2026-23025 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23025?
CVE-2026-23025 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23025?
A fix for CVE-2026-23025 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23025 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-2026-23025

Explore →

Is Your Infrastructure Affected by CVE-2026-23025?

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

Book a Demo →Browse All CVEs