Answer in brief
CVE-2026-68293 records a Unknown severity vulnerability in net/mlx5: Fix MCIA register buffer overflow on 32 dword reads. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=271907ee2f29cd1078fd219f0778fd824fb1971c <5be4eebd5a3a198dab0adcd550e1cadca79bdfed || >=271907ee2f29cd1078fd219f0778fd824fb1971c <87b39a8c875ca744b7de69af0a8ef8874cffccf1 || >=271907ee2f29cd1078fd219f0778fd824fb1971c <88b2a16ddac3357e3f1d528e758b51e2c945d546 || >=271907ee2f29cd1078fd219f0778fd824fb1971c <11c057d23465c7a5817a7284c896d19d54c0b616 | 5be4eebd5a3a198dab0adcd550e1cadca79bdfed, 87b39a8c875ca744b7de69af0a8ef8874cffccf1, 88b2a16ddac3357e3f1d528e758b51e2c945d546, 11c057d23465c7a5817a7284c896d19d54c0b616 |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68293 records a Unknown severity vulnerability in net/mlx5: Fix MCIA register buffer overflow on 32 dword reads. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=271907ee2f29cd1078fd219f0778fd824fb1971c <5be4eebd5a3a198dab0adcd550e1cadca79bdfed || >=271907ee2f29cd1078fd219f0778fd824fb1971c <87b39a8c875ca744b7de69af0a8ef8874cffccf1 || >=271907ee2f29cd1078fd219f0778fd824fb1971c <88b2a16ddac3357e3f1d528e758b51e2c945d546 || >=271907ee2f29cd1078fd219f0778fd824fb1971c <11c057d23465c7a5817a7284c896d19d54c0b616 | 5be4eebd5a3a198dab0adcd550e1cadca79bdfed, 87b39a8c875ca744b7de69af0a8ef8874cffccf1, 88b2a16ddac3357e3f1d528e758b51e2c945d546, 11c057d23465c7a5817a7284c896d19d54c0b616 |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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 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.
Quoted source text, attributed separately from HOL analysis.