- 7.1HighCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 97% of all CVEs (11 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Affected products
- affected 271907ee2f29cd1078fd219f0778fd824fb1971c – < 5ed6d41029832b11bc204d7cc326cf309d073666
- affected 271907ee2f29cd1078fd219f0778fd824fb1971c – < c8a4acc19dcdc83e1303c29d9535e5c99415a2e3
- affected 271907ee2f29cd1078fd219f0778fd824fb1971c – < 5be4eebd5a3a198dab0adcd550e1cadca79bdfed
- affected 271907ee2f29cd1078fd219f0778fd824fb1971c – < 87b39a8c875ca744b7de69af0a8ef8874cffccf1
- affected 271907ee2f29cd1078fd219f0778fd824fb1971c – < 88b2a16ddac3357e3f1d528e758b51e2c945d546
- affected 271907ee2f29cd1078fd219f0778fd824fb1971c – < 11c057d23465c7a5817a7284c896d19d54c0b616
- affected 5.18
- unaffected < 5.18
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/5ed6d41029832b11bc204d7cc326cf309d073666 (opens in a new tab)
- https://git.kernel.org/stable/c/c8a4acc19dcdc83e1303c29d9535e5c99415a2e3 (opens in a new tab)
- https://git.kernel.org/stable/c/5be4eebd5a3a198dab0adcd550e1cadca79bdfed (opens in a new tab)
- https://git.kernel.org/stable/c/87b39a8c875ca744b7de69af0a8ef8874cffccf1 (opens in a new tab)
- https://git.kernel.org/stable/c/88b2a16ddac3357e3f1d528e758b51e2c945d546 (opens in a new tab)
- https://git.kernel.org/stable/c/11c057d23465c7a5817a7284c896d19d54c0b616 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55394 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68293)Record last updated .