CVE-2025-40250

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

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

Also known asEUVD-2025-201207 (ENISA EUVD) · GHSA-fj2x-2whx-fgch (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:

net/mlx5: Clean up only new IRQ glue on request_irq() failure

The mlx5_irq_alloc() function can inadvertently free the entire rmap and end up in a crash[1] when the other threads tries to access this, when request_irq() fails due to exhausted IRQ vectors. This commit modifies the cleanup to remove only the specific IRQ mapping that was just added.

This prevents removal of other valid mappings and ensures precise cleanup of the failed IRQ allocation's associated glue object.

Note: This error is observed when both fwctl and rds configs are enabled.

[1] mlx5_core 0000:05:00.0: Successfully registered panic handler for port 1 mlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to request irq. err = -28 infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while trying to test write-combining support mlx5_core 0000:05:00.0: Successfully unregistered panic handler for port 1 mlx5_core 0000:06:00.0: Successfully registered panic handler for port 1 mlx5_core 0000:06:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to request irq. err = -28 infiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while trying to test write-combining support mlx5_core 0000:06:00.0: Successfully unregistered panic handler for port 1 mlx5_core 0000:03:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to request irq. err = -28 mlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to request irq. err = -28 general protection fault, probably for non-canonical address 0xe277a58fde16f291: 0000 [#1] SMP NOPTI

RIP: 0010:free_irq_cpu_rmap+0x23/0x7d Call Trace: ? show_trace_log_lvl+0x1d6/0x2f9 ? show_trace_log_lvl+0x1d6/0x2f9 ? mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core] ? __die_body.cold+0x8/0xa ? die_addr+0x39/0x53 ? exc_general_protection+0x1c4/0x3e9 ? dev_vprintk_emit+0x5f/0x90 ? asm_exc_general_protection+0x22/0x27 ? free_irq_cpu_rmap+0x23/0x7d mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core] irq_pool_request_vector+0x7d/0x90 [mlx5_core] mlx5_irq_request+0x2e/0xe0 [mlx5_core] mlx5_irq_request_vector+0xad/0xf7 [mlx5_core] comp_irq_request_pci+0x64/0xf0 [mlx5_core] create_comp_eq+0x71/0x385 [mlx5_core] ? mlx5e_open_xdpsq+0x11c/0x230 [mlx5_core] mlx5_comp_eqn_get+0x72/0x90 [mlx5_core] ? xas_load+0x8/0x91 mlx5_comp_irqn_get+0x40/0x90 [mlx5_core] mlx5e_open_channel+0x7d/0x3c7 [mlx5_core] mlx5e_open_channels+0xad/0x250 [mlx5_core] mlx5e_open_locked+0x3e/0x110 [mlx5_core] mlx5e_open+0x23/0x70 [mlx5_core] __dev_open+0xf1/0x1a5 __dev_change_flags+0x1e1/0x249 dev_change_flags+0x21/0x5c do_setlink+0x28b/0xcc4 ? __nla_parse+0x22/0x3d ? inet6_validate_link_af+0x6b/0x108 ? cpumask_next+0x1f/0x35 ? __snmp6_fill_stats64.constprop.0+0x66/0x107 ? __nla_validate_parse+0x48/0x1e6 __rtnl_newlink+0x5ff/0xa57 ? kmem_cache_alloc_trace+0x164/0x2ce rtnl_newlink+0x44/0x6e rtnetlink_rcv_msg+0x2bb/0x362 ? __netlink_sendskb+0x4c/0x6c ? netlink_unicast+0x28f/0x2ce ? rtnl_calcit.isra.0+0x150/0x146 netlink_rcv_skb+0x5f/0x112 netlink_unicast+0x213/0x2ce netlink_sendmsg+0x24f/0x4d9 __sock_sendmsg+0x65/0x6a ____sys_sendmsg+0x28f/0x2c9 ? import_iovec+0x17/0x2b ___sys_sendmsg+0x97/0xe0 __sys_sendmsg+0x81/0xd8 do_syscall_64+0x35/0x87 entry_SYSCALL_64_after_hwframe+0x6e/0x0 RIP: 0033:0x7fc328603727 Code: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 0b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 44 ed ff ff 48 RSP: 002b:00007ffe8eb3f1a0 EFLAGS: 00000293 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007fc328603727 RDX: 0000000000000000 RSI: 00007ffe8eb3f1f0 RDI: 000000000000000d RBP: 00007ffe8eb3f1f0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000 R13: 00000000000 ---truncated---

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 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
6th
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

December 4, 2025

Last Modified

October 19, 2026

Advisory Details (5)

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

SSA-253495

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

net/mlx5: Clean up only new IRQ glue on request_irq() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: Clean up only new IRQ glue on request_irq() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ebd02cf2dde11b86f89ea4c9f55179eab30d4ee
Web page

net/mlx5: Clean up only new IRQ glue on request_irq() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69e043bce09c9a77e5f55b9ac7505874a2a1a9f0
Web page

net/mlx5: Clean up only new IRQ glue on request_irq() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d6b4bea8b80bfa13c903ba547538249e7c5e977

Vendor Advisories for CVE-2025-40250(2)

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-106.106) @ noble2026-11-03ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-11-03ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-11-03ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-11-03ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-11-03ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-11-03ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-11-03ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-11-03ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9) @ questing2026-11-03ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-11-03ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-11-03ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-11-03ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9~24.04.1) @ noble2026-11-03ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1010.10) @ questing2026-11-03ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-11-03ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-11-03ubuntu
linuxKernel @ 6.6.118 (fixes >=6.4.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

(2 across 2 ecosystems)
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

(16)

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 / 50× 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 241 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 143 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-40250?
CVE-2025-40250 is a high-severity vulnerability; its CVE record was published on December 4, 2025. In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Clean up only new IRQ glue on request_irq() failure The mlx5_irq_alloc() function can inadvertently free the entire rmap and end up in a crash[1] when the other threads tries to access this, when request_irq() fails due…
When was the CVE record for CVE-2025-40250 published?
The CVE record for CVE-2025-40250 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 19, 2026; the record at its source may have been updated since.
Is CVE-2025-40250 actively exploited?
CVE-2025-40250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-40250?
CVE-2025-40250 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-40250?
A fix for CVE-2025-40250 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-40250 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-40250

Explore →

Is Your Infrastructure Affected by CVE-2025-40250?

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

Book a Demo →Browse All CVEs