CVE-2026-64210

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 11, 2026

Advisory Details (2)

Auto-updated Jul 27, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🔴 Active Exploitation

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

https://git.kernel.org/stable/c/c326f9c68921e2f14dfcecb2f6b4216313d50248
generic🔴 Active Exploitation

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(3)

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 rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(3)

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 29× in last 7d / 165× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 194 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64210?
CVE-2026-64210 is a high vulnerability 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 CVE-2026-64210 disclosed?
CVE-2026-64210 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64210 actively exploited?
CVE-2026-64210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64210?
CVE-2026-64210 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64210, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.