CVE-2026-72342
Received Received - Intake

Race Condition in Linux Kernel MLX5e HV VHCA Stats Handling

Vulnerability report for CVE-2026-72342, 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 agent registration race mlx5e_hv_vhca_stats_create() registers the stats agent through mlx5_hv_vhca_agent_create(). The helper publishes the agent in hv_vhca->agents[type] under agents_lock and immediately schedules an asynchronous control invalidation on the HV VHCA workqueue before returning to mlx5e. The asynchronous invalidation invokes the control agent's invalidate callback, which reads the hypervisor control block and forwards the command to mlx5e_hv_vhca_stats_control(). That callback may either: - call cancel_delayed_work_sync(&priv->stats_agent.work), or - call queue_delayed_work(priv->wq, &sagent->work, sagent->delay). However, the delayed_work and priv->stats_agent.agent are only initialized after mlx5_hv_vhca_agent_create() returns to mlx5e: agent = mlx5_hv_vhca_agent_create(...); /* publish + invalidate */ ... priv->stats_agent.agent = agent; /* too late */ INIT_DELAYED_WORK(&priv->stats_agent.work, ...); /* too late */ If the asynchronous control path runs before the two assignments above, it can: - Operate on an uninitialized delayed_work whose timer.function is NULL. queue_delayed_work() calls add_timer() unconditionally, so when the timer expires the timer softirq invokes a NULL function pointer. - Re-initialize the timer later through INIT_DELAYED_WORK() while the timer is already enqueued in the timer wheel, corrupting the hlist (entry.pprev cleared while the previous bucket node still points at this entry). - When the worker eventually runs, mlx5e_hv_vhca_stats_work() reads sagent->agent (NULL) and dereferences it inside mlx5_hv_vhca_agent_write(). Fix this by: - Initializing priv->stats_agent.work before invoking mlx5_hv_vhca_agent_create(), so the work is always in a valid state when the control callback observes it. - Adding a struct mlx5_hv_vhca_agent **ctx_update out-parameter to mlx5_hv_vhca_agent_create(). The helper writes the agent pointer to *ctx_update before publishing into hv_vhca->agents[] and triggering the agents_update flow, so any callback subsequently invoked from that flow already sees a valid priv->stats_agent.agent. This avoids having the control callback participate in agent initialization. While at it, access priv->stats_agent.agent with READ_ONCE()/WRITE_ONCE() for the cross-CPU access with the worker, and clear priv->stats_agent.buf on the agent_create() failure path.

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 linux_kernel *

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 is a race condition in the Linux kernel's mlx5e driver for Mellanox ConnectX network adapters. It occurs when initializing a stats agent for a virtual device. The issue arises because the agent's work structure is initialized after the agent is published, leading to potential NULL pointer dereferences or timer corruption if the async control path runs prematurely.

Detection Guidance

This vulnerability is specific to the Linux kernel's mlx5e driver for Mellanox NICs. Detection requires checking the kernel version and loaded modules. Use commands like 'uname -a' to check kernel version and 'lsmod | grep mlx5' to verify if the vulnerable module is loaded.

Impact Analysis

This vulnerability could cause system crashes due to NULL pointer dereferences or timer corruption. It may lead to kernel panics or instability in systems using Mellanox ConnectX adapters with SR-IOV virtualization enabled. Exploitable only in specific kernel configurations with mlx5e driver.

Compliance Impact

This vulnerability is a race condition in the Linux kernel's mlx5e driver that could lead to NULL pointer dereferences and memory corruption. It does not directly impact data privacy or security controls required by GDPR or HIPAA, as it is a low-level driver issue without evidence of data exposure or unauthorized access.

Mitigation Strategies

Immediate mitigation involves updating the Linux kernel to a patched version that includes the fix for CVE-2026-72342. Check your distribution's security advisories for kernel updates. If an update is not immediately available, consider disabling the mlx5e driver if not required.

Chat Assistant

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

EPSS Chart