CVE-2026-64210

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. A secondary CVSS source baseline 7.5; 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-2026-48618 (ENISA EUVD) · GHSA-p5xx-69g5-8564 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/mlx5e: xsk: Fix unlocked writing to ICOSQ

During napi poll, when the affinity changes and there's still XSK work to be done, we trigger an ICOSQ interrupt on the new CPU. However, this triggering on the ICOSQ is done unprotected.

There are 2 such races:

A) mlx5e_trigger_irq() is called while mlx5e_xsk_alloc_rx_mpwqe() is running from a different CPU due to affinity change. This can happen because IRQ triggering is done after napi_complete_done(). At this point the NAPI can be scheduled on a different CPU. Like this:

CPU A (old affinity, NAPI tail) CPU B (new affinity, fresh NAPI) ------------------------------- -------------------------------- napi_complete_done() clears SCHED mlx5e_cq_arm(...) napi_schedule_prep() sets SCHED mlx5e_napi_poll() mlx5e_xsk_alloc_rx_mpwqe() mlx5e_icosq_sync_lock() // noop memcpy 640 B UMR body advance sq->pc by 10 mlx5e_trigger_irq(&c->icosq) wqe_info[pi] = {NOP, 1} mlx5e_post_nop() advances sq->pc

B) mlx5e_trigger_irq() is called on the ICOSQ when mlx5e_trigger_napi_icosq() is running.

The obvious fix would be to lock the ICOSQ. But ICOSQ has an optimized locking scheme that doesn't work for this scenario. Kick the async ICOSQ instead which is always locked.

This issue was noticed in the wild with the following splat:

netdevice: ge-0-0-1: Bad OP in ICOSQ CQE: 0xd WARNING: drivers/net/ethernet/mellanox/mlx5/core/en_rx.c:826 [...] [...] Call Trace: mlx5e_napi_poll+0x11d/0x7f0 [mlx5_core] __napi_poll+0x30/0x200 ? skb_defer_free_flush+0x9c/0xc0 net_rx_action+0x2fe/0x3f0 handle_softirqs+0xd8/0x340 __irq_exit_rcu+0xbc/0xe0 common_interrupt+0x85/0xa0 asm_common_interrupt+0x26/0x40 [...] ---[ end trace 0000000000000000 ]--- mlx5_core 0000:08:00.0 ge-0-0-1: Error cqe on cqn 0x548, ci 0x2022, qn 0x8f4, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000030: 00 00 00 00 01 00 68 02 01 00 08 f4 de 14 59 d2 WQE DUMP: WQ size 16384 WQ cur size 0, WQE index 0x1e14, len: 64 00000000: 00 00 00 01 d9 ed 80 02 00 00 00 01 d9 ed 90 02 00000010: 00 00 00 01 d9 ed a0 02 00 00 00 01 d9 ed b0 02 00000020: 00 00 00 01 d9 ed c0 02 00 00 00 01 d9 ed d0 02 00000030: 00 00 00 01 d9 ed e0 02 00 00 00 01 d9 ed f0 02 mlx5_core 0000:08:00.0 ge-0-0-1: Error cqe on cqn 0x548, ci 0x2023, qn 0x8f4, opcode 0xd, syndrome 0x5, vendor syndrome 0xf9 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000030: 00 00 00 00 01 00 f9 05 01 00 08 f4 de 15 cf d2

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
30th
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: 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 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)14 days if the affected system is publicly exposed; 60 days if it is not.

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

July 24, 2026

Last Modified

October 19, 2026

Advisory Details (2)

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

net/mlx5e: xsk: Fix unlocked writing to ICOSQ - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5e: xsk: Fix unlocked writing to ICOSQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d3b91e7d81000d295cd914d4d9d6f860252e2bf

Vendor Advisories for CVE-2026-64210(2)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-27ubuntu

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:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

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 11× in last 7d / 62× 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 358 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 258 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64210?
CVE-2026-64210 is a high-severity vulnerability; its CVE record was published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: xsk: Fix unlocked writing to ICOSQ During napi poll, when the affinity changes and there's still XSK work to be done, we trigger an ICOSQ interrupt on the new CPU. However, this triggering on the ICOSQ is done…
When was the CVE record for CVE-2026-64210 published?
The CVE record for CVE-2026-64210 was published on July 24, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-64210 actively exploited?
CVE-2026-64210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64210?
CVE-2026-64210 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64210?
A fix for CVE-2026-64210 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64210 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-64210

Explore →

Is Your Infrastructure Affected by CVE-2026-64210?

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

Book a Demo →Browse All CVEs