CVE-2026-68293

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM 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 — 4 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.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
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.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or 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 (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
Patch available.
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(6)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-687.50.1.el9_82026-09-23redhat
redhatkernel-0:6.12.0-211.58.1.el10_22026-09-23redhat
redhatkernel-0:4.18.0-553.166.1.el8_102026-09-22redhat
redhatkernel-rt-0:4.18.0-553.166.1.rt7.507.el8_102026-09-22redhat

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 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Data Freshness Timeline

(refreshed 30× in last 7d / 111× 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 208 total refreshes for this CVE.

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

Related CVEs(same vendor)

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 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.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68293?
CVE-2026-68293 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68293?
A fix for CVE-2026-68293 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68293 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-68293

Explore →

Is Your Infrastructure Affected by CVE-2026-68293?

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

Book a Demo →Browse All CVEs