CVE-2026-64034 Overview
CVE-2026-64034 is a Time-of-Check Time-of-Use (TOCTOU) double-fetch vulnerability in the Linux kernel's Microsoft Azure Network Adapter (MANA) driver. The flaw resides in the mana_hwc_rx_event_handler() function, which reads resp->response.hwc_msg_id from DMA-coherent memory, performs a bounds check, and then re-reads the same field in mana_hwc_handle_resp() for use in test_bit() and pointer arithmetic. Because DMA-coherent memory is uncached on x86 and shared unencrypted in Confidential VMs such as SEV-SNP and TDX, a malicious hypervisor or hardware component can modify the value between the check and the use, bypassing bounds validation.
Critical Impact
A malicious host or hardware entity can bypass kernel bounds checks in Confidential VMs, enabling out-of-bounds memory access and potential guest kernel compromise.
Affected Products
- Linux kernel builds that include the net: mana driver prior to the fix commits
- Confidential VM guests on Azure using SEV-SNP or Intel TDX with the MANA network adapter
- Distributions shipping unpatched stable kernel branches referenced by the upstream commits
Discovery Timeline
- 2026-07-19 - CVE-2026-64034 published to NVD
- 2026-07-20 - Last updated in NVD database
Technical Details for CVE-2026-64034
Vulnerability Analysis
The vulnerability is a TOCTOU double-fetch in the MANA hardware channel receive path. The driver services responses placed by the host into a DMA-coherent buffer shared with the guest. In mana_hwc_rx_event_handler(), the driver first reads hwc_msg_id from the shared buffer and validates it against the expected bounds. The subsequent call to mana_hwc_handle_resp() reads the same field again from the same buffer, using it to index bitmaps via test_bit() and to compute pointers.
Because the memory is host-visible and uncached, the second load fetches the current value from host memory rather than a cached copy. A hostile host or peripheral can rewrite hwc_msg_id in the window between the two reads, satisfying the initial validation with a benign value and then supplying an out-of-bounds value for the actual use.
Root Cause
The root cause is unsafe reuse of an untrusted field stored in DMA-coherent, host-shared memory. The driver treats the buffer as stable across two accesses, which is incorrect for memory that a peer with write access can modify at any time. This class of flaw is especially relevant to Confidential Computing threat models, where the hypervisor is untrusted.
Attack Vector
Exploitation requires an attacker who controls the host side of the MANA hardware channel, such as a malicious or compromised hypervisor targeting a Confidential VM guest. The attacker races writes to hwc_msg_id in the DMA buffer to defeat the guest kernel's bounds check, then steers test_bit() and pointer arithmetic in mana_hwc_handle_resp() to out-of-bounds locations. Successful exploitation can lead to guest kernel memory corruption or information disclosure.
No public exploit code is available. The fix reads hwc_msg_id exactly once using READ_ONCE() into a stack-local variable in mana_hwc_rx_event_handler() and passes the validated value as a parameter to mana_hwc_handle_resp(), eliminating the second fetch from shared memory.
Detection Methods for CVE-2026-64034
Indicators of Compromise
- Unexpected kernel oops, warnings, or panics originating in mana_hwc_handle_resp() or adjacent MANA driver functions.
- Anomalous bit-test failures or memory access faults referencing hwc_msg_id values outside documented ranges.
- Confidential VM guests logging MANA hardware channel errors immediately after host-side maintenance or migration events.
Detection Strategies
- Inventory running kernels across Azure Confidential VM fleets and compare build hashes against the fixed upstream commits (09ec063, 35f0f0a, 3c4db56, 566f42f, 6180a06, 70ad2df, a201c66).
- Alert on kernel crash telemetry that includes MANA driver frames, particularly on SEV-SNP or TDX guests.
- Correlate guest kernel warnings with host hypervisor change events to identify potential exploitation windows.
Monitoring Recommendations
- Forward guest dmesg and kdump artifacts to a central log store and search for mana_hwc_ symbols in stack traces.
- Track kernel package versions in Configuration Management databases and flag hosts still running vulnerable builds.
- Monitor Confidential VM attestation reports and pair them with kernel version telemetry to ensure patched images are in use.
How to Mitigate CVE-2026-64034
Immediate Actions Required
- Identify all Linux hosts running the MANA driver, prioritizing Confidential VMs on Azure using SEV-SNP or TDX.
- Apply distribution kernel updates that incorporate the upstream fix commits listed in the kernel.org references.
- Reboot affected guests after patching to ensure the updated kernel is active.
Patch Information
The fix reads hwc_msg_id once via READ_ONCE() in mana_hwc_rx_event_handler() and passes the validated value to mana_hwc_handle_resp(), preventing a second fetch from DMA-coherent memory. The change is available in multiple stable branches through commits 09ec063, 35f0f0a, 3c4db56, 566f42f, 6180a06, 70ad2df, and a201c66.
Workarounds
- No supported workaround exists; the driver is required for network connectivity on affected Azure Confidential VM SKUs.
- Where patching is delayed, restrict Confidential VM deployment to trusted host regions and enforce strict attestation policies until the kernel update is deployed.
- Rebuild and redeploy custom VM images with a patched kernel rather than relying on runtime mitigations.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
