CVE-2025-21675

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-01-31. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-2624 (ENISA EUVD) · GHSA-wfp2-gq58-rf57 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/mlx5: Clear port select structure when fail to create

Clear the port select structure on error so no stale values left after definers are destroyed. That's because the mlx5_lag_destroy_definers() always try to destroy all lag definers in the tt_map, so in the flow below lag definers get double-destroyed and cause kernel crash:

mlx5_lag_port_sel_create() mlx5_lag_create_definers() mlx5_lag_create_definer() <- Failed on tt 1 mlx5_lag_destroy_definers() <- definers[tt=0] gets destroyed mlx5_lag_port_sel_create() mlx5_lag_create_definers() mlx5_lag_create_definer() <- Failed on tt 0 mlx5_lag_destroy_definers() <- definers[tt=0] gets double-destroyed

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 Mem abort info: ESR = 0x0000000096000005 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x05: level 1 translation fault Data abort info: ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 64k pages, 48-bit VAs, pgdp=0000000112ce2e00 [0000000000000008] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000 Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP Modules linked in: iptable_raw bonding ip_gre ip6_gre gre ip6_tunnel tunnel6 geneve ip6_udp_tunnel udp_tunnel ipip tunnel4 ip_tunnel rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) ib_uverbs(OE) mlx5_fwctl(OE) fwctl(OE) mlx5_core(OE) mlxdevm(OE) ib_core(OE) mlxfw(OE) memtrack(OE) mlx_compat(OE) openvswitch nsh nf_conncount psample xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc netconsole overlay efi_pstore sch_fq_codel zram ip_tables crct10dif_ce qemu_fw_cfg fuse ipv6 crc_ccitt [last unloaded: mlx_compat(OE)] CPU: 3 UID: 0 PID: 217 Comm: kworker/u53:2 Tainted: G OE 6.11.0+ #2 Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 Workqueue: mlx5_lag mlx5_do_bond_work [mlx5_core] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : mlx5_del_flow_rules+0x24/0x2c0 [mlx5_core] lr : mlx5_lag_destroy_definer+0x54/0x100 [mlx5_core] sp : ffff800085fafb00 x29: ffff800085fafb00 x28: ffff0000da0c8000 x27: 0000000000000000 x26: ffff0000da0c8000 x25: ffff0000da0c8000 x24: ffff0000da0c8000 x23: ffff0000c31f81a0 x22: 0400000000000000 x21: ffff0000da0c8000 x20: 0000000000000000 x19: 0000000000000001 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffff8b0c9350 x14: 0000000000000000 x13: ffff800081390d18 x12: ffff800081dc3cc0 x11: 0000000000000001 x10: 0000000000000b10 x9 : ffff80007ab7304c x8 : ffff0000d00711f0 x7 : 0000000000000004 x6 : 0000000000000190 x5 : ffff00027edb3010 x4 : 0000000000000000 x3 : 0000000000000000 x2 : ffff0000d39b8000 x1 : ffff0000d39b8000 x0 : 0400000000000000 Call trace: mlx5_del_flow_rules+0x24/0x2c0 [mlx5_core] mlx5_lag_destroy_definer+0x54/0x100 [mlx5_core] mlx5_lag_destroy_definers+0xa0/0x108 [mlx5_core] mlx5_lag_port_sel_create+0x2d4/0x6f8 [mlx5_core] mlx5_activate_lag+0x60c/0x6f8 [mlx5_core] mlx5_do_bond_work+0x284/0x5c8 [mlx5_core] process_one_work+0x170/0x3e0 worker_thread+0x2d8/0x3e0 kthread+0x11c/0x128 ret_from_fork+0x10/0x20 Code: a9025bf5 aa0003f6 a90363f7 f90023f9 (f9400400) ---[ end trace 0000000000000000 ]---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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
13th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-10-25). 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, 2025

Last Modified

November 3, 2025

References (5)

Vendor Advisories for CVE-2025-21675(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-azure (6.11.0-1013.13) @ oracular2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2024.25) @ noble2026-10-24ubuntu
ubuntulinux-tools-realtime (6.8.1-1023.24) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1029.33) @ noble2026-10-24ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1031.33) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1030.35) @ noble2026-10-24ubuntu
ubuntulinux-virtual (6.8.0-62.65) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-24.24+1) @ oracular2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-64.67~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1018.19) @ noble2026-10-24ubuntu
linuxKernel @ 6.1.127 (fixes >=5.16.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.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (34 versions)
  • every version up to 6.1.128-1: fixed in 6.1.128-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.11-1: fixed in 6.12.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.11-1: fixed in 6.12.11-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 7× in last 7d / 38× 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 96 of 195 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-21675?
CVE-2025-21675 is a medium-severity vulnerability; its CVE record was published on January 31, 2025. In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Clear port select structure when fail to create Clear the port select structure on error so no stale values left after definers are destroyed. That's because the mlx5_lag_destroy_definers() always try to destroy all lag…
When was the CVE record for CVE-2025-21675 published?
The CVE record for CVE-2025-21675 was published on January 31, 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 November 3, 2025; the record at its source may have been updated since.
Is CVE-2025-21675 actively exploited?
CVE-2025-21675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21675?
CVE-2025-21675 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21675?
A fix for CVE-2025-21675 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21675 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-21675

Explore →

Is Your Infrastructure Affected by CVE-2025-21675?

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

Book a Demo →Browse All CVEs