CVE-2026-68293

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

net/mlx5: Fix MCIA register buffer overflow on 32 dword reads

The MCIA register can return up to 32 dwords (128 bytes) when the device advertises the mcia_32dwords capability, but struct mlx5_ifc_mcia_reg_bits only defines dword_0..11, leaving room for just 12 dwords (48 bytes) of data.

mlx5_query_mcia() clamps the read size to mlx5_mcia_max_bytes() and then memcpy()s that many bytes out of the register, potentially reading past the end of the 'out' buffer. On kernels built with FORTIFY_SOURCE this is caught as a buffer overflow while reading the module EEPROM via ethtool:

detected buffer overflow in memcpy kernel BUG at lib/string_helpers.c:1048! RIP: 0010:fortify_panic+0x13/0x20 Call Trace: mlx5_query_mcia.isra.0+0x200/0x210 [mlx5_core] mlx5_query_module_eeprom_by_page+0x4a/0xa0 [mlx5_core] mlx5e_get_module_eeprom_by_page+0xbb/0x120 [mlx5_core] eeprom_prepare_data+0xf3/0x170 ethnl_default_doit+0xf1/0x3b0

Extend the mcia_reg layout to 32 dwords.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

net/mlx5: Fix MCIA register buffer overflow on 32 dword reads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88b2a16ddac3357e3f1d528e758b51e2c945d546
generic

net/mlx5: Fix MCIA register buffer overflow on 32 dword reads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87b39a8c875ca744b7de69af0a8ef8874cffccf1
generic

net/mlx5: Fix MCIA register buffer overflow on 32 dword reads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5be4eebd5a3a198dab0adcd550e1cadca79bdfed
generic

net/mlx5: Fix MCIA register buffer overflow on 32 dword reads - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11c057d23465c7a5817a7284c896d19d54c0b616

Vendor Advisories for CVE-2026-68293(2)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 44× 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.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:43 UTCGHSA enrichment
  3. 2026-08-20 11:39 UTCGHSA enrichment
  4. 2026-08-20 00:34 UTCEG score recompute
  5. 2026-08-20 00:34 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 13:30 UTCGHSA enrichment
  8. 2026-08-19 02:25 UTCGHSA enrichment
  9. 2026-08-18 15:18 UTCEG score recompute
  10. 2026-08-18 15:18 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 03:45 UTCGHSA enrichment
  14. 2026-08-17 16:41 UTCEG score recompute
  15. 2026-08-17 16:41 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:37 UTCEG score recompute
  18. 2026-08-17 05:37 UTCGHSA enrichment
  19. 2026-08-17 05:07 UTCEG score recompute
  20. 2026-08-17 05:07 UTCGHSA enrichment
  21. 2026-08-16 18:10 UTCEG score recompute
  22. 2026-08-16 18:10 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 07:05 UTCEG score recompute
  25. 2026-08-16 07:05 UTCGHSA enrichment
Show 19 more
  1. 2026-08-15 20:02 UTCGHSA enrichment
  2. 2026-08-15 08:58 UTCEG score recompute
  3. 2026-08-15 08:58 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 21:54 UTCGHSA enrichment
  6. 2026-08-14 10:50 UTCEG score recompute
  7. 2026-08-14 10:50 UTCGHSA enrichment
  8. 2026-08-13 23:46 UTCEG score recompute
  9. 2026-08-13 23:46 UTCGHSA enrichment
  10. 2026-08-13 22:44 UTCEG score recompute▲ 7.10
  11. 2026-08-13 22:44 UTCGHSA enrichment
  12. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 19:13 UTCEG score recompute
  15. 2026-08-13 19:13 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-10 13:24 UTCNVD update
  18. 2026-08-10 12:19 UTCEG score recompute
  19. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68293?
CVE-2026-68293 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix MCIA register buffer overflow on 32 dword reads The MCIA register can return up to 32 dwords (128 bytes) when the device advertises the mcia_32dwords capability, but struct mlx5ifcmciaregbits only defines dword_0..11,…
When was CVE-2026-68293 disclosed?
CVE-2026-68293 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68293 actively exploited?
CVE-2026-68293 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 96.3% of all scored CVEs.
What is the CVSS score of CVE-2026-68293?
CVE-2026-68293 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-68293?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68293, 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

Explore the affected products and dependency analysis for CVE-2026-68293

Explore →

Is Your Infrastructure Affected by CVE-2026-68293?

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

Start Free Scan →Browse All CVEs