Skip to main content

Linux Kernel EUVDEUVD-2026-45591

| CVE-2026-64018 CRITICAL
2026-07-19 Linux GHSA-r2vm-q278-6vpv
9.3
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
9.3 CRITICAL
AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI
8.1 HIGH

Attacker is the untrusted host (PR:N, AV:L) but must run a Confidential VM with MANA and win a shared-memory modification window, so AC:H; host-to-guest crossing is S:C with full C/I/A impact.

3.1 AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
CRITICAL
qualitative
Red Hat
7.0 HIGH
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 16:53 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
9.3 (CRITICAL)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:39 cve.org
CRITICAL 9.3
CVE Published
Jul 19, 2026 - 15:39 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

net: mana: validate rx_req_idx to prevent out-of-bounds array access

In mana_hwc_rx_event_handler(), rx_req_idx is derived from sge->address in DMA-coherent memory. In Confidential VMs (SEV-SNP/TDX), this memory is shared unencrypted and HW can modify WQE contents at any time. No bounds check exists on rx_req_idx, which can lead to an out-of-bounds access into reqs[].

Add bounds check on rx_req_idx in mana_hwc_rx_event_handler() before using it to index the reqs[] array.

AnalysisAI

Out-of-bounds array access in the Linux kernel's Microsoft Azure Network Adapter (mana) driver lets a malicious hypervisor corrupt guest kernel memory within Confidential VMs. In mana_hwc_rx_event_handler(), the rx_req_idx index is read from host-shared DMA-coherent memory (a WQE's sge->address) without a bounds check, so in SEV-SNP/TDX guests the untrusted host can steer the index to read/write past the reqs[] array. There is no public exploit identified at time of analysis and EPSS is low (0.17%), consistent with a defense-in-depth hardening fix for the confidential-computing threat model rather than an actively exploited flaw.

Technical ContextAI

MANA is the paravirtualized NIC Microsoft exposes to Linux guests on Azure; its driver uses a hardware channel (HWC) where receive completions are described by Work Queue Entries (WQEs) in DMA-coherent memory shared between guest and host. In standard VMs this memory is trusted, but under AMD SEV-SNP and Intel TDX Confidential VMs the guest's shared/unencrypted bounce region can be modified by the host or emulated device at any time. mana_hwc_rx_event_handler() derived rx_req_idx from sge->address and used it directly to index the reqs[] request array with no validation, so attacker-controlled WQE contents translate into an out-of-bounds array access (the Tags label this a buffer-overflow class issue; NVD lists no specific CWE, but this maps to CWE-129 improper validation of array index / CWE-125/787 out-of-bounds read/write). The CPE data is generic (cpe:2.3:a:linux:linux:*), so exact affected trees come from the EUVD/stable-tree references rather than the CPE strings.

RemediationAI

Update to a kernel that adds the rx_req_idx bounds check in mana_hwc_rx_event_handler(): Vendor-released patch versions are 5.15.209, 6.1.175, 6.6.142, 6.12.92, 6.18.34, 7.0.11 and mainline 7.1 - apply the fixed build for your distribution's series via your distro's kernel update channel. The corresponding upstream commits are published on git.kernel.org (e.g. https://git.kernel.org/stable/c/5ddc715324badd7f2641bc177db1d027b402adae, https://git.kernel.org/stable/c/fa627a5eaa83fc0261f44ef3769693b886ca6e27 and the other stable backports listed in the references). Since the issue only matters under the confidential-computing threat model, an interim compensating control is to run affected workloads as standard (non-Confidential) VMs where the host is already in the trust boundary, or to avoid the MANA-backed CoCo configuration until patched - the trade-off is losing memory-encryption/attestation guarantees, so this should be a short-term measure only. There is no relevant in-guest configuration toggle to disable, as the exposure is inherent to the mana receive path.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-45591 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy