CVE-2025-40261

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-04. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 5 sources updated this week

Also known asEUVD-2025-201196 (ENISA EUVD) · GHSA-9x2f-7mf8-f579 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl()

nvme_fc_delete_assocation() waits for pending I/O to complete before returning, and an error can cause ->ioerr_work to be queued after cancel_work_sync() had been called. Move the call to cancel_work_sync() to be after nvme_fc_delete_association() to ensure ->ioerr_work is not running when the nvme_fc_ctrl object is freed. Otherwise the following can occur:

[ 1135.911754] list_del corruption, ff2d24c8093f31f8->next is NULL [ 1135.917705] ------------[ cut here ]------------ [ 1135.922336] kernel BUG at lib/list_debug.c:52! [ 1135.926784] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 1135.931851] CPU: 48 UID: 0 PID: 726 Comm: kworker/u449:23 Kdump: loaded Not tainted 6.12.0 #1 PREEMPT(voluntary) [ 1135.943490] Hardware name: Dell Inc. PowerEdge R660/0HGTK9, BIOS 2.5.4 01/16/2025 [ 1135.950969] Workqueue: 0x0 (nvme-wq) [ 1135.954673] RIP: 0010:__list_del_entry_valid_or_report.cold+0xf/0x6f [ 1135.961041] Code: c7 c7 98 68 72 94 e8 26 45 fe ff 0f 0b 48 c7 c7 70 68 72 94 e8 18 45 fe ff 0f 0b 48 89 fe 48 c7 c7 80 69 72 94 e8 07 45 fe ff <0f> 0b 48 89 d1 48 c7 c7 a0 6a 72 94 48 89 c2 e8 f3 44 fe ff 0f 0b [ 1135.979788] RSP: 0018:ff579b19482d3e50 EFLAGS: 00010046 [ 1135.985015] RAX: 0000000000000033 RBX: ff2d24c8093f31f0 RCX: 0000000000000000 [ 1135.992148] RDX: 0000000000000000 RSI: ff2d24d6bfa1d0c0 RDI: ff2d24d6bfa1d0c0 [ 1135.999278] RBP: ff2d24c8093f31f8 R08: 0000000000000000 R09: ffffffff951e2b08 [ 1136.006413] R10: ffffffff95122ac8 R11: 0000000000000003 R12: ff2d24c78697c100 [ 1136.013546] R13: fffffffffffffff8 R14: 0000000000000000 R15: ff2d24c78697c0c0 [ 1136.020677] FS: 0000000000000000(0000) GS:ff2d24d6bfa00000(0000) knlGS:0000000000000000 [ 1136.028765] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1136.034510] CR2: 00007fd207f90b80 CR3: 000000163ea22003 CR4: 0000000000f73ef0 [ 1136.041641] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1136.048776] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 [ 1136.055910] PKRU: 55555554 [ 1136.058623] Call Trace: [ 1136.061074] [ 1136.063179] ? show_trace_log_lvl+0x1b0/0x2f0 [ 1136.067540] ? show_trace_log_lvl+0x1b0/0x2f0 [ 1136.071898] ? move_linked_works+0x4a/0xa0 [ 1136.075998] ? __list_del_entry_valid_or_report.cold+0xf/0x6f [ 1136.081744] ? __die_body.cold+0x8/0x12 [ 1136.085584] ? die+0x2e/0x50 [ 1136.088469] ? do_trap+0xca/0x110 [ 1136.091789] ? do_error_trap+0x65/0x80 [ 1136.095543] ? __list_del_entry_valid_or_report.cold+0xf/0x6f [ 1136.101289] ? exc_invalid_op+0x50/0x70 [ 1136.105127] ? __list_del_entry_valid_or_report.cold+0xf/0x6f [ 1136.110874] ? asm_exc_invalid_op+0x1a/0x20 [ 1136.115059] ? __list_del_entry_valid_or_report.cold+0xf/0x6f [ 1136.120806] move_linked_works+0x4a/0xa0 [ 1136.124733] worker_thread+0x216/0x3a0 [ 1136.128485] ? __pfx_worker_thread+0x10/0x10 [ 1136.132758] kthread+0xfa/0x240 [ 1136.135904] ? __pfx_kthread+0x10/0x10 [ 1136.139657] ret_from_fork+0x31/0x50 [ 1136.143236] ? __pfx_kthread+0x10/0x10 [ 1136.146988] ret_from_fork_asm+0x1a/0x30 [ 1136.150915]

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

December 4, 2025

Last Modified

October 18, 2026

Advisory Details (10)

Auto-updated Oct 28, 2026
Patch available.
Web page

SSA-253495

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

SSA-082556

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

SSA-019113

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

nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9610a2c162ef729a3988213a4604376e492f6f44
Web page

nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48ae433c6cc6985f647b1b37d8bb002972cf9bdb
Web page

nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f48cd7f35da07fc067cef926bb7f6f4735de37b
Web page

nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33f64600a12055219bda38b55320c62cdeda9167
Web page

nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a2c5495b6d1ecb0fa18ef6631450f391a888256

Vendor Advisories for CVE-2025-40261(2)

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

Patch Availability(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-11-02ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-11-02ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-11-02ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-11-02ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9) @ questing2026-11-02ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-11-02ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-11-02ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-11-02ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-11-02ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-11-02ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-11-02ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9~24.04.1) @ noble2026-11-02ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-11-02ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-11-02ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-11-02ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-11-02ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-11-02ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-11-02ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-11-02ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-11-02ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1010.10) @ questing2026-11-02ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-11-02ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-11-02ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-11-02ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-11-02ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-11-02ubuntu
linuxKernel @ 5.10.247 (fixes >=0)—osv
linuxKernel @ 5.10.253 (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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)
  • every version up to 5.10.247-1: fixed in 5.10.247-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.158-1~deb11u1 (13 versions)
  • every version up to 6.1.159-1~deb11u1: fixed in 6.1.159-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)
  • every version up to 6.12.63-1: fixed in 6.12.63-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.9-1 (81 versions)
  • every version up to 6.17.10-1: fixed in 6.17.10-1
—

Additional Vendor Advisories

(24)

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 28× in last 7d / 116× 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 100 of 315 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. None are among the latest 100 rows. The 215 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-40261?
CVE-2025-40261 is a critical-severity vulnerability; its CVE record was published on December 4, 2025. In the Linux kernel, the following vulnerability has been resolved: nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() nvme_fc_delete_assocation() waits for pending I/O to complete before returning, and an error can cause ->ioerr_work to be queued after cancel_work_sync() had…
When was the CVE record for CVE-2025-40261 published?
The CVE record for CVE-2025-40261 was published on December 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 18, 2026; the record at its source may have been updated since.
Is CVE-2025-40261 actively exploited?
CVE-2025-40261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-40261?
CVE-2025-40261 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-40261?
A fix for CVE-2025-40261 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-40261 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-40261

Explore →

Is Your Infrastructure Affected by CVE-2025-40261?

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

Book a Demo →Browse All CVEs