[CVE-2026-64210][MODERATE 7.0] net/mlx5e: xsk: Fix unlocked writing to ICOSQ [ Upstream

[CVE-2026-64210][MODERATE 7.0] net/mlx5e: xsk: Fix unlocked writing to ICOSQ [ Upstream

[AL-KERNEL]

CVE: CVE-2026-64210
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net/mlx5e: xsk: Fix unlocked writing to ICOSQ [ Upstream
Commit: 8d3b91e7d81000d295cd914d4d9d6f860252e2bf
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8d3b91e7d81000d295cd914d4d9d6f860252e2bf
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64210
Analysis date: Fri, 24 Jul 2026 12:33:39 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A race in the mlx5e XSK zero-copy NAPI path can perform unlocked ICOSQ writes during affinity changes, corrupting device work queue state and causing bad CQEs or network device disruption, with practical impact primarily as local or delegated-networking DoS.

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

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

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-64210	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';CWE-362;CWE-667;CWE-662;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.8';DESCR 'A race in the mlx5e XSK zero-copy path can cause unlocked writes to the ICOSQ when NAPI affinity changes while XSK work is still pending. One CPU can be preparing UMR work queue entries while another CPU posts a NOP through mlx5e_trigger_irq(), which can corrupt ICOSQ state and produce bad CQEs or warnings from the mlx5 driver. For the CVSS the PR:L is used in the paranoid score because a reduced privilege local service account or delegated network administration context may be able to control AF_XDP or XSK operation in some deployments. The issue is not directly network reachable by packet traffic alone, although traffic may help keep the XSK path busy after the local setup exists. Impact is primarily denial of service through queue corruption or network device disruption, with limited C and I only as a cautious manual-review signal for hardware WQE corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)  SKIP CVE-2026-64210 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE LOCK RACE NETWORK HARDWARE  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=5
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**

## 2. Signal breakdown

Conservative signals:

* +1 Reliable kernel crash / strong DoS: the issue was observed in the wild with Bad OP in ICOSQ CQE, mlx5 warning, and device error CQEs.
* +1 Weak/indirect corruption candidate: the race corrupts ICOSQ WQE state, but the patch does not show attacker-controlled arbitrary overwrite, UAF reclaim, type confusion, or callback control.
* +1 Privileged kernel/device-management corruption path: corruption occurs in mlx5e NIC work queue handling, involving device-visible WQEs and DMA-adjacent driver state.
* -1 Hard or unreliable race / special timing required: the race depends on NAPI affinity change while XSK work remains pending.
* -1 Highly constrained corruption: the corrupted data is ICOSQ/WQE state with limited evidence of attacker-controlled payload or target.
* 0 to -1 Configuration specificity: requires mlx5e, XSK zero-copy path, and affinity-change timing. I do not apply a strong rarity penalty because mlx5 is common in data-center networking and the bug was seen in the wild.

Paranoid additions:

* +1 Firmware-mediated or device-mediated external influence: the corrupted WQEs are consumed by the NIC/firmware path, and traffic can help keep the XSK path active after local setup.
* +1 Confidentiality/integrity concern, limited: not proven, but hardware WQE corruption can affect DMA-facing state enough to justify manual review sensitivity.
* +1 Availability impact beyond a simple WARN: bad CQEs and queue/device disruption are more actionable than a harmless warning.

Not awarded:

* No +2 remote reachable: ordinary packet traffic alone is not enough without the local XSK/NAPI setup.
* No +2 strong LPE plausibility: no UAF reclaim, arbitrary write, controlled overwrite, type confusion, callback dispatch, or refcount takeover is shown.
* No strong generic memory corruption: this is constrained device queue corruption, not a demonstrated kernel heap overwrite primitive.

## 3. Reachability analysis

The realistic trigger requires the mlx5e driver, XSK zero-copy support, pending XSK work, and an affinity change during NAPI polling. In typical deployments, setting up XSK/XDP and queue steering often requires CAP_NET_ADMIN, root, or a privileged networking service, so the conservative interpretation is not local-unprivileged.

However, the paranoid score treats PR as lower in practical environments where a reduced-privilege service account, container root with delegated networking, or a dataplane process controls AF_XDP/XSK operation. The path is not directly network reachable by packets alone, but traffic can contribute to keeping the affected path busy once the local setup exists.

Call-site confidence: high. The patch directly changes the affected mlx5e_napi_poll call site from an unlocked ICOSQ trigger to the locked async ICOSQ path.

## 4. Severity interpretation

This behaves more like an actionable Moderate issue than an ordinary low-priority driver warning. The demonstrated impact is device queue corruption and DoS, not proven privilege escalation. The theoretical concern is that corruption occurs in a device-visible WQE path, but the patch does not support classifying it as arbitrary memory corruption or a strong LPE primitive.

The paranoid score reaches 5 because this is a real race in a DMA-adjacent NIC queue path observed in production-like conditions, and because reduced-privilege networking services may make the trigger more practical than full host-root only.

## 5. One-sentence report phrase

A race in the mlx5e XSK zero-copy NAPI path can perform unlocked ICOSQ writes during affinity changes, corrupting device work queue state and causing bad CQEs or network device disruption, with practical impact primarily as local or delegated-networking DoS.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Manual review is required because the bug corrupts NIC work queue state in a DMA-adjacent driver path and the practical privilege boundary depends heavily on whether AF_XDP/XSK control is delegated to reduced-privilege services or containers.

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

Patch: net/mlx5e: xsk: Fix unlocked writing to ICOSQ [ Upstream
Commit: 8d3b91e7d81000d295cd914d4d9d6f860252e2bf
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8d3b91e7d81000d295cd914d4d9d6f860252e2bf

Changed files:
  drivers/net/ethernet/mellanox/mlx5/core/en_rx.c
  drivers/net/ethernet/mellanox/mlx5/core/en_txrx.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=8d3b91e7d81000d295cd914d4d9d6f860252e2bf

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

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

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:L/I:L/A:H
  The Best / paranoid CVSS score: 5.8

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: 5

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