[CVE-2026-72342][MODERATE 7.0] net/mlx5e: Fix HV VHCA stats agent registration race [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-72342
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: net/mlx5e: Fix HV VHCA stats agent registration race [ Upstream
Commit: b0fd6d3bb06182f19f3b59a53f57b5098b99048a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b0fd6d3bb06182f19f3b59a53f57b5098b99048a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72342
Analysis date: Sat, 15 Aug 2026 19:17:09 -0400
ActionableScore: 6
ActionableScore lower bound: 3
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
A race in mlx5e HV VHCA stats agent registration can let an asynchronous control callback access uninitialized delayed_work and agent state, causing NULL dereference, NULL timer callback execution, or timer hlist corruption with at least kernel crash impact and possible higher memory corruption risk.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72342 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72342

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-72342	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';CWE-362;CWE-665;**CWE-476;CWE-667;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A race in mlx5e HV VHCA stats agent registration can allow the asynchronous control invalidation path to run before stats_agent.work and stats_agent.agent are fully initialized. This can operate on an uninitialized delayed_work object, enqueue a timer with a NULL function pointer, reinitialize a timer that is already queued, or later dereference a NULL agent pointer in the stats worker. The direct effect is a kernel crash or hang, but the timer hlist corruption makes this a memory corruption candidate rather than a pure warning only issue. For the CVSS the PR:L is used in the paranoid score because delegated network administration, a service account, or a reduced root environment may be able to trigger device reconfiguration or driver reload paths, although typical systems require administrator control. The issue is not directly network reachable and depends on Mellanox mlx5 HV VHCA support and a narrow asynchronous initialization race. Impact is at least local denial of service and in the worst still defensible case may allow confidentiality or integrity impact due to memory corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 5)  SKIP CVE-2026-72342 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE WRITE OOB INIT RACE NETWORK HARDWARE KPANIC 	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=6
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 6
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Paranoid score signals:

* Firmware-mediated external influence: +1. The race is driven through the HV VHCA agent and hypervisor control/invalidation flow rather than an ordinary userspace-only path.
* Memory corruption, weak/indirect corruption candidate: +1. The patch describes reinitializing an already queued timer and corrupting the timer hlist, but does not show attacker-controlled payload or target selection.
* Real lifetime/init-order corruption: +1. The asynchronous callback can observe `stats_agent.work` and `stats_agent.agent` before they are initialized.
* Reliable kernel crash / strong DoS: +1. The commit explicitly describes NULL timer function invocation and NULL agent dereference.
* Weak LPE concern: +1. Timer-list corruption in kernel workqueue/timer infrastructure is more concerning than a pure NULL dereference, although no practical privilege-escalation primitive is demonstrated.
* Privileged kernel/device-management memory corruption path: +1. The corruption occurs in a trusted Mellanox mlx5 device-management/statistics agent path.
* Confidentiality impact plausible: +1. Only for paranoid scoring, due to memory corruption candidate status.
* Integrity impact plausible: +1. Only for paranoid scoring, due to timer hlist corruption.
* Hard or unreliable race / special timing required: -1. The vulnerable window is a narrow async initialization race.
* Rare AND difficult-to-reach subsystem/configuration: -1. Requires mlx5 HV VHCA support and the relevant stats agent path.

Conservative interpretation keeps the issue closer to firmware/device-assisted DoS with weak corruption evidence and limited reachability.

## 3. Reachability analysis

The most realistic trigger requires Mellanox mlx5 HV VHCA support and execution of the stats agent registration path. In typical deployments, forcing driver load, reload, or device reconfiguration is administrative, but the actual vulnerable callback is driven by an asynchronous HV VHCA control invalidation flow. Namespaces or containers do not obviously make this reachable by a fully unprivileged user, but delegated device or network administration, service accounts, or reduced-root environments could lower the practical privilege boundary. The path is not directly network reachable.

Call-site confidence: high. The commit message and patch show the relevant create path, asynchronous publication point, callback consequences, and worker dereference.

## 4. Severity interpretation

This is not an ordinary low-risk driver warning. The direct demonstrated impact is kernel crash or hang, but the timer hlist corruption makes it an actionable memory-corruption candidate. Realistic exploitation beyond DoS is not demonstrated, and the race plus rare hardware/HV configuration limit broad exposure. Still, because the corruption affects core timer/workqueue state, this should be treated as Actionable Moderate at minimum and reviewed as a possible Important candidate.

## 5. One-sentence report phrase

A race in mlx5e HV VHCA stats agent registration can let an asynchronous control callback access uninitialized delayed_work and agent state, causing NULL dereference, NULL timer callback execution, or timer hlist corruption with at least kernel crash impact and possible higher memory corruption risk.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED.

Reason: the patch explicitly describes timer hlist corruption and asynchronous initialization/lifetime misuse, which is stronger than a simple NULL pointer dereference even though a practical LPE primitive is not demonstrated.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: net/mlx5e: Fix HV VHCA stats agent registration race [ Upstream
Commit: b0fd6d3bb06182f19f3b59a53f57b5098b99048a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b0fd6d3bb06182f19f3b59a53f57b5098b99048a

Changed files:
  drivers/net/ethernet/mellanox/mlx5/core/en/hv_vhca_stats.c
  drivers/net/ethernet/mellanox/mlx5/core/lib/hv_vhca.c
  drivers/net/ethernet/mellanox/mlx5/core/lib/hv_vhca.h

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b0fd6d3bb06182f19f3b59a53f57b5098b99048a

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72342 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72342

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 3
  Paranoid ActionableScore: 6

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).