[CVE-2026-72341][MODERATE REGULAR] net/mlx5e: Fix publication race for priv->channel_stats[] [ Upstream

[CVE-2026-72341][MODERATE REGULAR] net/mlx5e: Fix publication race for priv->channel_stats[] [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72341
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net/mlx5e: Fix publication race for priv->channel_stats[] [ Upstream
Commit: 5c7e3755abf663f033de24f917b77685e9543045
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5c7e3755abf663f033de24f917b77685e9543045
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72341
Analysis date: Sat, 15 Aug 2026 18:38:30 -0400
ActionableScore: 4
ActionableScore lower bound: 2
Actionable bucket: Borderline manual review recommended / Ordinary Moderate with production DoS evidence
Manual review required: YES

Summary:
A publication race in mlx5e channel statistics can let a local stats reader observe `stats_nch` before the matching `channel_stats` pointer is visible on weakly ordered architectures, causing a NULL pointer dereference and kernel crash during NIC bringup.

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

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

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 REGULAR
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-72341	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-362;CWE-662;**CWE-476;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'mlx5e has a publication race for priv channel_stats and stats_nch on weakly ordered architectures. A reader can observe an increased stats_nch value before the corresponding channel_stats pointer is visible, then dereference a NULL channel_stats entry while collecting network statistics. This was observed on BlueField-3 DPU systems when ovs-vswitchd queried netdev statistics over netlink during NIC bringup. For the CVSS the PR:L is used because a local user or local service able to query netlink network statistics can participate in the trigger, while reliable exploitation also depends on a concurrent driver bringup or channel allocation event. The issue is not directly network reachable through packet traffic. Impact is denial of service via kernel crash.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended / Ordinary Moderate with production DoS evidence (with actual score 3)  SKIP CVE-2026-72341 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE WRITE OOB NULLPTR RACE NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	checked

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

ActionableScore=4
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 4
* Final recommended bucket: **Borderline manual review recommended / Ordinary Moderate with production DoS evidence**::

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The commit shows an observed NULL pointer dereference in production on BlueField-3 during stats collection.
* Broad datacenter driver exposure: +1. mlx5e is common in server and DPU deployments, although this is not a generic networking core path.
* Hard or timing-dependent race: -1. Trigger depends on a publication ordering race during channel allocation or NIC bringup.
* Weakly ordered architecture / deployment specificity: -1. The issue primarily affects ARM, PowerPC, RISC-V style memory ordering and was observed on arm64 BlueField.

Conservative total: 2.

Paranoid signals:

* Local unprivileged or low-privileged trigger surface: +1. Reading network statistics via netlink or related tooling may be available to local users or local services, even though reliable triggering also needs concurrent driver bringup.
* Reliable kernel crash / strong DoS: +1. The crash path is concrete and shown in the commit.
* Broad datacenter driver exposure: +1. mlx5e is widely used in high-value networking and DPU environments.
* Availability impact realistic: +1. The impact is a host kernel crash in a production-observed path, not just a WARN.

Paranoid total: 4.

Not awarded:

* Remote reachable: +0. Packet traffic alone is not shown to trigger the bug.
* Generic memory corruption: +0. The demonstrated primitive is NULL pointer dereference, not UAF, OOB write, type confusion, or controlled overwrite.
* Privilege escalation plausible: +0. No reclaim, stale object reuse, write primitive, callback control, or object confusion is shown.

## 3. Reachability analysis

The bug is triggered by concurrent mlx5e channel stats publication and stats reading. A reader can observe `stats_nch` before the corresponding `channel_stats[]` pointer is visible, then dereference NULL.

The demonstrated path is local control-plane activity: `ovs-vswitchd` queries netdev statistics over netlink while NIC bringup allocates channel stats on another CPU. A local user or service may be able to query statistics, but reliable triggering also depends on a concurrent device bringup or channel allocation event. Administrative control may be needed to create that timing reliably.

Namespaces and containers may lower practical privilege requirements if a container or service has delegated network visibility or access to relevant netlink stats, but this is not a direct remote packet-processing bug.

## 4. Severity interpretation

This behaves like an ordinary Moderate or borderline actionable Moderate issue, not an Important-class vulnerability.

The realistic impact is kernel crash / DoS on affected systems. Theoretical memory-corruption escalation is not supported by the patch because the failure mode is a NULL pointer dereference caused by weak memory ordering, not a freed object, attacker-controlled replacement, overwrite, refcount misuse, or callback corruption.

Manual review is still reasonable because the issue was observed in production, affects a widely deployed high-value network driver, and depends on architecture-specific ordering semantics that can be missed by automated triage.

## 5. One-sentence report phrase

A publication race in mlx5e channel statistics can let a local stats reader observe `stats_nch` before the matching `channel_stats` pointer is visible on weakly ordered architectures, causing a NULL pointer dereference and kernel crash during NIC bringup.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED.
YES REQUIRES MANUAL CHECK.

Reason: this is not strong memory corruption or remote exploitation, but it is a production-observed race in a common datacenter network driver with a reliable kernel crash path.

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

Patch: net/mlx5e: Fix publication race for priv->channel_stats[] [ Upstream
Commit: 5c7e3755abf663f033de24f917b77685e9543045
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5c7e3755abf663f033de24f917b77685e9543045

Changed files:
  drivers/net/ethernet/mellanox/mlx5/core/en.h
  drivers/net/ethernet/mellanox/mlx5/core/en/hv_vhca_stats.c
  drivers/net/ethernet/mellanox/mlx5/core/en_main.c
  drivers/net/ethernet/mellanox/mlx5/core/en_stats.c
  drivers/net/ethernet/mellanox/mlx5/core/ipoib/ipoib.c

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=5c7e3755abf663f033de24f917b77685e9543045

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

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

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:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

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: 2
  Paranoid ActionableScore: 4

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: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

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).