[CVE-2026-64034][MODERATE 7.0] net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer [ Upstream

[CVE-2026-64034][MODERATE 7.0] net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer [ Upstream

[AL-KERNEL]

CVE: CVE-2026-64034
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer [ Upstream
Commit: a201c66edf2ebc6cfdc3813a889ba20fecebfae3
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a201c66edf2ebc6cfdc3813a889ba20fecebfae3
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64034
Analysis date: Sun, 19 Jul 2026 18:50:24 -0400
ActionableScore: 7
ActionableScore lower bound: 4
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
A TOCTOU double-fetch in the MANA HWC receive path allows a malicious device or virtualization host to change a DMA-visible `hwc_msg_id` after validation, leading to out-of-bounds or wrong-context kernel driver access with at least DoS impact and plausible confidentiality or integrity risk.

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

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

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-64034	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H';CWE-367;CWE-125;CWE-119;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7.5';DESCR 'A TOCTOU double fetch exists in the MANA HWC receive path because hwc_msg_id is read from DMA coherent memory for bounds checking and then read again from the same DMA buffer during response handling. A malicious or compromised device or virtualization host can change the DMA visible value between the check and the use, causing the validated index to differ from the index used for test_bit and caller_ctx pointer arithmetic. For the CVSS the PR:N is used because no privileges inside the victim guest are required when the attacker controls the device side or host visible DMA memory. The issue is not a normal Internet remote packet path and is better modeled as AV:A across a device or virtualization boundary. Impact is at least denial of service via invalid memory access or kernel crash, and the paranoid score uses CIA:HHH because the patch context shows a bounds check bypass with attacker influenced indexing into kernel driver state.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 6)	YES	REMOTE READ SIMPLEFIX ERRORPATH NETWORK DMAorINTERRUPT TEST KPANIC  KPANIC INCREASED_TO_HIGH_BASED_ON_GUESSCVSS KPANIC DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN7	NO	NO	checked

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

ActionableScore=7
ActionableScoreLower=4

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative signals:

* Firmware-mediated external influence: +1. The attacker model is a malicious or compromised device, host, or hypervisor modifying DMA-visible memory, not ordinary Internet traffic.
* Memory corruption, weak/indirect corruption candidate: +1. The patch fixes a bounds-check bypass where an attacker-influenced `hwc_msg_id` can be re-read and used for `test_bit()` and `caller_ctx` pointer arithmetic.
* Privileged kernel/device-management memory corruption path: +1. The affected path is DMA-adjacent MANA device response handling in a trusted kernel driver context.
* Availability impact realistic: +1. An out-of-bounds index or invalid `caller_ctx` selection can plausibly crash or destabilize the driver/kernel.

Paranoid additional signals:

* Weak LPE concern: +1. The primitive is not a demonstrated arbitrary write, but attacker-influenced object selection in kernel driver state is enough to require manual review.
* Confidentiality impact plausible: +1. Out-of-bounds or wrong-context response handling may expose or mix kernel driver state, although no direct leak is demonstrated.
* Integrity impact plausible: +1. Wrong `caller_ctx` selection may complete or modify the wrong in-flight operation, giving a plausible integrity concern.
* No strong remote-reachable bonus. This is not a normal network packet path.
* No strong corruption primitive bonus. The patch does not demonstrate an OOB write, UAF reclaim, arbitrary write, or controlled overwrite.

## 3. Reachability analysis

The realistic trigger is a malicious or compromised hardware device, firmware, host, or virtualization layer able to modify DMA-coherent memory between two loads. In Confidential VM settings such as SEV-SNP or TDX, the commit explicitly notes that this memory remains shared and host-visible, making the threat model relevant.

Local namespaces and containers do not materially change reachability, because the trigger is outside the guest userspace privilege model. For the victim guest, no local privileges are required if the attacker controls the host/device side, but this is still better modeled as firmware/device-mediated or adjacent rather than Internet remote.

The path is specific to Microsoft MANA hardware/virtual NIC deployments, especially Azure-like environments. It is not a universal networking core path, but it is security-relevant in cloud and CVM deployments.

Call-site confidence: high. The patch shows both the initial bounds check and the later use in `test_bit()` and `caller_ctx + msg_id`.

## 4. Severity interpretation

This is stronger than an ordinary Moderate because it is a DMA double-fetch TOCTOU bug with a validated value being replaced before pointer arithmetic in kernel driver state. The conservative interpretation is Actionable Moderate at minimum because the concrete primitive is an attacker-influenced index after bounds-check bypass, but no direct arbitrary write or demonstrated LPE is shown.

The paranoid interpretation reaches Strong Important candidate because the affected boundary is host/device-to-guest DMA, the attacker can potentially control the second fetched value, and the use site selects kernel driver context. This creates plausible confidentiality and integrity concerns beyond a simple crash, even though practical privilege escalation is not demonstrated.

## 5. One-sentence report phrase

A TOCTOU double-fetch in the MANA HWC receive path allows a malicious device or virtualization host to change a DMA-visible `hwc_msg_id` after validation, leading to out-of-bounds or wrong-context kernel driver access with at least DoS impact and plausible confidentiality or integrity risk.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

This should not be auto-closed because the patch fixes a DMA-visible bounds-check bypass where attacker-controlled hardware or host-side memory can influence kernel pointer arithmetic after validation. The demonstrated primitive is not enough to claim reliable LPE, but it is sufficient for Important-candidate manual analysis.

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

Patch: net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer [ Upstream
Commit: a201c66edf2ebc6cfdc3813a889ba20fecebfae3
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a201c66edf2ebc6cfdc3813a889ba20fecebfae3

Changed files:
  drivers/net/ethernet/microsoft/mana/hw_channel.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=a201c66edf2ebc6cfdc3813a889ba20fecebfae3

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

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

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

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