CVE-2026-72343
Received Received - Intake

Buffer Overflow in Linux Kernel mlx5e Driver

Vulnerability report for CVE-2026-72343, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation mlx5e_hv_vhca_stats_create() is called from mlx5e_nic_enable(), before mlx5e_open(). At that point priv->stats_nch is still zero, because it is only ever incremented in mlx5e_channel_stats_alloc(), which is reached only from mlx5e_open_channel(). mlx5e_hv_vhca_stats_buf_size() therefore returns 0, and kvzalloc(0, GFP_KERNEL) returns ZERO_SIZE_PTR ((void *)16) rather than NULL. The "if (!buf)" guard does not catch this, and mlx5e_hv_vhca_stats_create() completes "successfully" with priv->stats_agent.buf set to ZERO_SIZE_PTR. Once channels are opened (priv->stats_nch > 0) and the hypervisor enables stats reporting, mlx5e_hv_vhca_stats_work() recomputes buf_len using the new non-zero stats_nch and calls memset(buf, 0, buf_len) on ZERO_SIZE_PTR, faulting at address 0x10. Allocate the buffer based on priv->max_nch, which is set in mlx5e_priv_init() and is the upper bound on stats_nch: - Add a separate helper mlx5e_hv_vhca_stats_buf_max_size() that returns sizeof(per_ring_stats) * max(max_nch, stats_nch), and use it for the kvzalloc() in mlx5e_hv_vhca_stats_create(). - Keep mlx5e_hv_vhca_stats_buf_size() (which returns based on stats_nch) for the worker's active payload size, so the wire format (block->rings = stats_nch) and the amount of data filled by mlx5e_hv_vhca_fill_stats() are unchanged. The max(max_nch, stats_nch) guard handles the rare case where mlx5e_attach_netdev() recomputes max_nch downward across a detach/resume cycle while priv->stats_nch persists (mlx5e_detach_netdev does not call mlx5e_priv_cleanup, so stats_nch is only reset when the netdev is destroyed). Without the guard, the worker could compute buf_len from stats_nch and overrun the smaller buffer allocated based on the reduced max_nch. Allocating a non-zero buffer also makes the kvzalloc() failure path in mlx5e_hv_vhca_stats_create() reachable for the first time: it returns early without (re)creating the agent. Clear priv->stats_agent.{agent,buf} in mlx5e_hv_vhca_stats_destroy() after freeing them, so that if a later create() bails out on this path, a subsequent teardown does not double-free the stale agent/buffer left from a previous enable/disable cycle. This mirrors the existing mlx5e pattern of preallocating arrays of size max_nch (e.g. priv->channel_stats) and lazily populating entries up to stats_nch on demand.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-17
Generated
2026-09-04
AI Q&A
2026-08-15
EPSS Evaluated
2026-09-03
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
mlx mlx5e *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a buffer allocation issue in the mlx5e driver. When initializing network interfaces, a zero-sized buffer is allocated due to incorrect stats_nch value, leading to a ZERO_SIZE_PTR being used instead of NULL. Later, when stats reporting is enabled, a memset operation on this invalid pointer causes a kernel fault at address 0x10.

Detection Guidance

This vulnerability is specific to the Linux kernel's mlx5e driver for Mellanox NICs. Detection requires checking kernel logs for crashes or faults related to mlx5e_hv_vhca_stats_work() or ZERO_SIZE_PTR dereferences. Monitor for kernel oops or panics after enabling stats reporting. No direct commands are provided in the context.

Impact Analysis

This vulnerability can cause kernel crashes or instability on systems using the affected mlx5e driver. It may lead to denial-of-service conditions where the system becomes unresponsive or requires a reboot.

Compliance Impact

This vulnerability is a kernel-level memory corruption issue in the Linux net/mlx5e driver that could lead to a system crash due to a NULL pointer dereference. It does not directly affect data confidentiality, integrity, or availability in a way that would violate GDPR or HIPAA compliance requirements. However, system crashes could indirectly impact compliance by disrupting services handling sensitive data.

Mitigation Strategies

Apply the kernel patch that fixes the mlx5e_hv_vhca_stats_create() buffer allocation issue. Ensure your Linux kernel version includes the fix for CVE-2026-72343. If using Mellanox NICs, update the mlx5_core driver to a patched version. Monitor vendor advisories for updates.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72343. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart