Skip to main content

Linux Kernel EUVDEUVD-2026-39321

| CVE-2026-53230 HIGH
Out-of-bounds Read (CWE-125)
2026-06-25 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-pw9r-h2m6-6vvg
8.7
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
View

Attack ChainAIDerived

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

  1. Access
    Gain privileged access to mlx5 SR-IOV host
  2. Delivery
    Set VF MAC-list max above PF via devlink
  3. Exploit
    Trigger VF address-list change
  4. Execution
    Oversized firmware response overflows buffer
  5. Persist
    Out-of-bounds kernel slab read
  6. Impact
    Info leak or kernel panic

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

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

Exploitation Conditions

Requires a system using the mlx5_core driver with NVIDIA/Mellanox ConnectX hardware operating in SR-IOV / e-switch (switchdev) mode, AND a virtual function whose configured MAC-list maximum (log_max_current_uc_list / log_max_current_mc_list) has been set larger than the physical function's capability via devlink - this non-default, privileged configuration is the concrete prerequisite. The overflow then fires automatically when that VF's MAC address list changes, through the esw_vport_change_handler workqueue path. Limiting factors: it is not remotely reachable (AV:L), it depends on a privileged devlink configuration action and specific Mellanox/NVIDIA hardware, and the configuration is not present by default, so hosts without mlx5 SR-IOV or with VF MAC limits kept at/below the PF capability are not exposed.

Impact

Signals are mixed and lean toward moderate, config-gated risk rather than urgent mass exploitation. The supplied CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:C, base 8.7) reflects local access with low privileges and a scope change, but the description shows the real trigger is an out-of-bounds READ during automatic eswitch handling after an administrator has raised a VF's MAC-list maximum via devlink - a privileged, non-default configuration action. The most likely impact is information disclosure of adjacent kernel slab memory and/or a KASAN-detected crash/panic, not straightforward code execution; the supplied vector's C:H/I:L feels high for a 4-byte OOB read, so confidentiality impact may be overstated relative to the description. EPSS is low (0.18%, 7th percentile), there is no CISA KEV listing and no public exploit identified, consistent with a hardware- and configuration-specific kernel hardening fix. Net: a legitimate memory-safety defect worth patching on affected mlx5/SR-IOV hosts, but not a drop-everything internet-facing emergency. Conflict to verify with vendor: CVSS marks AV:L/PR:L while exploitation realistically depends on privileged devlink configuration of a VF - verify intended privilege level.

Exploit ScenarioDerived

On a host with an mlx5 NIC in SR-IOV mode, a privileged operator (or compromised management plane) raises a virtual function's MAC-list maximum via devlink above the PF's capability; when that VF's address list subsequently changes, the kernel's eswitch worker queries the vport and reads past the undersized slab buffer, leaking adjacent kernel memory or panicking the host. No public exploit code is identified at time of analysis, and the local attack vector plus dependency on privileged devlink configuration make opportunistic exploitation unlikely.

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 – Jun 28, 2026

Out-of-bounds kernel memory read in the Linux mlx5_core driver's mlx5_query_nic_vport_mac_list() function allows a slab-out-of-bounds access when querying a VF vport whose configured MAC-list maximum exceeds the PF's log_max_current_uc/mc_list capability. The driver sizes its firmware command buffer using the PF capabilities rather than the vport's own HCA caps, so an oversized firmware response overflows the buffer during eswitch vport-change handling. This affects systems running NVIDIA/Mellanox ConnectX (mlx5) NICs in SR-IOV/switchdev mode; no public exploit identified at time of analysis and EPSS exploitation probability is low (0.18%, 7th percentile).

RemediationAI

Vendor-released patch: update to a fixed Linux stable kernel - 6.6.143, 6.12.94, 6.18.36, 7.0.13, or 7.1 (or later) on the matching branch, drawing the corresponding stable commit from https://git.kernel.org/stable/c/ (e.g. 894e036a24a26a6dd7b17d8d3fb5c53ab48a6074). For distribution kernels, apply the vendor backport carrying these commits. If immediate patching is not possible, the practical compensating control is to avoid the triggering configuration: do not raise VF MAC-list maximums beyond the PF capability via devlink (keep VF unicast/multicast MAC-list limits at or below the PF's log_max_current_uc/mc_list), since the overflow only manifests when a VF's configured max exceeds the PF-derived buffer size; the trade-off is reduced per-VF MAC filtering capacity for tenants needing many addresses. Where feasible, restrict who can run privileged devlink/SR-IOV configuration (CAP_NET_ADMIN) on these hosts to limit who can reach the vulnerable path. There is no remote-network exposure to block, so firewall/port controls are not applicable.

Affected VersionsENISA

Linux e16aea2744abea612c27ee0eef606c6a6a8204de <894e036a24a26a6dd7b17d8d3fb5c53ab48a6074
Linux patch: 6.12.94
Linux patch: 7.1
Linux e16aea2744abea612c27ee0eef606c6a6a8204de <0f807764bb122fd63aa45f4229cb1ef2679fbd40
Linux e16aea2744abea612c27ee0eef606c6a6a8204de <2398e497389ed4be43f7cfbab499b49cec7dae1a
Linux patch: 6.18.36
Linux e16aea2744abea612c27ee0eef606c6a6a8204de <41781f2789309462520a93822e946521ed78f97f
Linux patch: 6.6.143
Linux patch: 0
Linux 4.5
Linux patch: 7.0.13
Linux e16aea2744abea612c27ee0eef606c6a6a8204de <537d87784e81c3d7037525b99416455cee088cdc

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 bug lives in the mlx5_core driver that operates NVIDIA/Mellanox ConnectX-series RDMA/Ethernet adapters, specifically in the e-switch (embedded switch / SR-IOV) MAC address management path. mlx5_query_nic_vport_mac_list() issues a QUERY_NIC_VPORT_CONTEXT firmware command and allocates a response buffer sized from the physical function's log_max_current_uc_list and log_max_current_mc_list capabilities. A virtual function's per-vport MAC-list maximum can be raised independently via devlink, so the firmware can return more entries than the PF-derived buffer can hold, and the parsing loop reads past the slab allocation (KASAN flags a 4-byte read past the end). This is a classic buffer-sizing/bounds error (CWE-125 Out-of-bounds Read / CWE-131 Incorrect Calculation of Buffer Size, though the feed lists CWE as N/A) reached from the kernel workqueue context esw_vport_change_handler -> esw_update_vport_addr_list. The fix queries the vport's own HCA capabilities to size the buffer correctly and refactors the function to allocate and return the MAC list internally.

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 (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY 8.7 HIGH
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:H
vuln.today AI 5.1 MEDIUM

Trigger requires privileged devlink configuration of a VF MAC-list max (PR:H) on local mlx5 hardware (AV:L); impact is a small OOB read causing potential info leak (C:L) and likely panic (A:H), no integrity change.

3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/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 (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

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

Lifecycle Timeline

4
CVSS changed
Jun 28, 2026 - 08:22 NVD
8.7 (HIGH)
Patch available
Jun 25, 2026 - 10:32 EUVD
CVE Published
Jun 25, 2026 - 09:16 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 25, 2026 - 09:16 cve.org
HIGH 8.7

DescriptionCVE.org

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

net/mlx5: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list

mlx5_query_nic_vport_mac_list() sizes its firmware command buffer using the PF's log_max_current_uc/mc_list capabilities. When querying a VF vport with a larger configured max (via devlink), the firmware response can overflow this buffer:

BUG: KASAN: slab-out-of-bounds in mlx5_query_nic_vport_mac_list+0x453/0x4c0 [mlx5_core] Read of size 4 at addr ff1100013ffc8a12 by task kworker/u96:2/385

CPU: 12 UID: 0 PID: 385 Comm: kworker/u96:2 Not tainted 7.0.0-rc6+ #1 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009) Workqueue: mlx5_esw_wq esw_vport_change_handler [mlx5_core] Call Trace: <TASK> dump_stack_lvl+0x69/0xa0 print_report+0x176/0x4e4 kasan_report+0xc8/0x100 mlx5_query_nic_vport_mac_list+0x453/0x4c0 [mlx5_core] esw_update_vport_addr_list+0x2e3/0xda0 [mlx5_core] esw_vport_change_handle_locked+0xa1f/0x1060 [mlx5_core] esw_vport_change_handler+0x6a/0x90 [mlx5_core] process_one_work+0x87f/0x15e0 worker_thread+0x62b/0x1020 kthread+0x375/0x490 ret_from_fork+0x4dc/0x810 ret_from_fork_asm+0x11/0x20 </TASK>

Fix by querying the vport's own HCA caps to size the buffer correctly. Refactor the function to allocate and return the MAC list internally, removing the caller's dependency on knowing the correct max.

Executive ViewAI

Why It Matters

CVE-2026-53230 in NVIDIA/Mellanox ConnectX network drivers affects Linux systems using SR-IOV virtualization, allowing unauthorized kernel memory access to sensitive data. Organizations operating virtualized infrastructure with these adapters face data exfiltration and system compromise risks; no public exploit identified at time of analysis.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
mlx5/ConnectX NICs common in datacenters but needs SR-IOV/eswitch configuration
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

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
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.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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