Skip to main content

Linux Kernel EUVDEUVD-2026-55394

| CVE-2026-68293 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-08-10 Linux GHSA-7555-mcj4-25r2
7.1
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local shell with CAP_NET_ADMIN
  2. Delivery
    identify mlx5 NIC with mcia_32dwords capability
  3. Exploit
    issue ethtool EEPROM page query
  4. Execution
    mlx5_query_mcia() reads 128 bytes into 48-byte buffer
  5. Persist
    FORTIFY_SOURCE triggers kernel BUG or OOB memory read
  6. Impact
    kernel panic (DoS) or kernel memory disclosure

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires: (1) local access with CAP_NET_ADMIN privilege (or equivalent - PR:L in CVSS), (2) a Mellanox/NVIDIA ConnectX network adapter using the mlx5 driver, and (3) the adapter must advertise the mcia_32dwords capability, which is a hardware-level feature present in newer ConnectX generations. The trigger is an ethtool EEPROM query (e.g., ethtool --module-info or --eeprom-dump targeting the NIC). Exploitation is NOT possible remotely - the attack vector is strictly local (AV:L). On FORTIFY_SOURCE-enabled kernels (virtually all distribution kernels), the result is a guaranteed kernel panic rather than exploitable memory corruption, limiting the real-world impact to denial of service. Non-default conditions: requires physical/logical local access, specific NIC hardware with mcia_32dwords support, and mlx5 driver loaded.

Impact

Real-world risk is moderate-to-low despite the 7.1 CVSS score. The CVSS vector (AV:L/AC:L/PR:L) correctly reflects that an attacker must have local access and low-privilege credentials - this is not remotely exploitable. The EPSS score of 0.18% at the 8th percentile confirms the security community assigns minimal near-term exploitation probability, consistent with the absence of public exploit code or KEV listing. The primary realistic impact is kernel panic (denial of service) triggered by issuing an ethtool EEPROM query on a vulnerable adapter; the confidentiality impact (C:H) represents potential out-of-bounds kernel memory disclosure, though exploiting this for meaningful data exfiltration would require additional primitives. The vulnerability is reliably triggered on FORTIFY_SOURCE-enabled kernels (most distro kernels), making the DoS vector easily exercised by any local user with CAP_NET_ADMIN. For environments running Mellanox mlx5 NICs with the mcia_32dwords capability (common in high-speed data center deployments), this warrants patching during the next maintenance window rather than emergency response.

Exploit ScenarioDerived

A low-privileged local user or container with CAP_NET_ADMIN issues an ethtool EEPROM page read command against a network interface backed by a Mellanox ConnectX adapter that advertises the mcia_32dwords capability. The mlx5 driver calls mlx5_query_mcia(), which calculates a read size of 128 bytes via mlx5_mcia_max_bytes() but memcpy()s into a struct sized for only 48 bytes, triggering either a FORTIFY_SOURCE kernel panic (DoS) or, on kernels without FORTIFY_SOURCE, silent out-of-bounds kernel memory access. No public exploit code exists at time of analysis, but the reproducibility is confirmed by the call trace in the CVE description itself.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 14, 2026

Buffer overflow in the Linux kernel's mlx5 network driver allows a local low-privileged attacker to crash the kernel or read out-of-bounds kernel memory when querying module EEPROM data via ethtool on systems equipped with Mellanox/NVIDIA ConnectX adapters that advertise the mcia_32dwords capability. The root cause is a struct size mismatch: mlx5_ifc_mcia_reg_bits defines only 12 dwords (48 bytes) of MCIA register storage while the hardware can return up to 32 dwords (128 bytes), causing mlx5_query_mcia() to memcpy beyond the allocated buffer. No public exploit has been identified at time of analysis and EPSS remains low at 0.18%, but the kernel BUG triggered by FORTIFY_SOURCE on patched builds confirms the overflow is reliably reproducible.

RemediationAI

The primary fix is to upgrade to a patched kernel version: 6.12.101, 6.18.42, 7.1.6, or any release based on 7.2-rc5 or later. The upstream fix extends mlx5_ifc_mcia_reg_bits to 32 dwords to match the maximum hardware-advertised size. Stable-branch commits are available at https://git.kernel.org/stable/c/5be4eebd5a3a198dab0adcd550e1cadca79bdfed, https://git.kernel.org/stable/c/87b39a8c875ca744b7de69af0a8ef8874cffccf1, https://git.kernel.org/stable/c/88b2a16ddac3357e3f1d528e758b51e2c945d546, and https://git.kernel.org/stable/c/11c057d23465c7a5817a7284c896d19d54c0b616. As a compensating control prior to patching, restrict CAP_NET_ADMIN to trusted administrators only, which prevents unprivileged local users from invoking ethtool EEPROM queries; note this does not eliminate risk for privileged insiders or compromised admin accounts. Alternatively, blocking ethtool module-eeprom subcommand access via user namespaces or seccomp policy in container environments limits the attack surface. FORTIFY_SOURCE (enabled by default in most distribution kernels) converts the overflow into a kernel BUG/panic rather than silent memory corruption, which limits exploitability for information disclosure but confirms the DoS vector.

Affected VersionsENISA

Linux patch: 7.1.6
Linux 271907ee2f29cd1078fd219f0778fd824fb1971c <87b39a8c875ca744b7de69af0a8ef8874cffccf1
Linux 271907ee2f29cd1078fd219f0778fd824fb1971c <11c057d23465c7a5817a7284c896d19d54c0b616
Linux patch: 7.2-rc5
Linux patch: 6.12.101
Linux 271907ee2f29cd1078fd219f0778fd824fb1971c <5be4eebd5a3a198dab0adcd550e1cadca79bdfed
Linux patch: 6.18.42
Linux 271907ee2f29cd1078fd219f0778fd824fb1971c <88b2a16ddac3357e3f1d528e758b51e2c945d546
Linux 5.18
Linux patch: 0

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The mlx5 driver (net/mlx5) supports Mellanox/NVIDIA ConnectX-series high-speed NICs, which are pervasive in cloud and enterprise data center environments. The MCIA (Module Control Interface Access) register is used to read transceiver/optical module EEPROM data via the ethtool interface. The affected code path is mlx5_query_mcia() → mlx5_query_module_eeprom_by_page() → mlx5e_get_module_eeprom_by_page() → eeprom_prepare_data(). When a device advertises the mcia_32dwords capability, mlx5_mcia_max_bytes() correctly returns 128 bytes; however, the 'out' buffer is backed by struct mlx5_ifc_mcia_reg_bits which only defines fields dword_0 through dword_11 (48 bytes). The subsequent memcpy of up to 128 bytes into this undersized structure constitutes a classic stack/heap buffer overflow. The affected CPE is cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* with the vulnerability introduced at commit 271907ee2f29cd1078fd219f0778fd824fb1971c (Linux 5.18). The CWE is not formally assigned, but the root cause class is CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) / CWE-131 (Incorrect Calculation of Buffer Size).

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.1 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
vuln.today AI 7.1 HIGH

Local access with low privileges (CAP_NET_ADMIN) required to invoke ethtool; no integrity impact; high confidentiality and availability from OOB read and kernel panic.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat 7.0 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

4
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.1 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 12:02 cve.org
HIGH 7.1
CVE Published
Aug 10, 2026 - 12:02 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A buffer overflow vulnerability affecting Mellanox/NVIDIA ConnectX network adapters on Linux systems can allow local users to trigger kernel crashes or extract sensitive kernel memory using standard ethtool commands, creating both availability and information security risks. Organizations with this network hardware face potential production downtime and exposure of kernel-level data to unprivileged local users. Remediation via vendor patch is available and should be expedited across vulnerable systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
High
mlx5 NICs widely deployed in cloud and enterprise data centers
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy