CVE-2026-99591

Description

A flaw was found in the Linux kernel's AMD Input-Output Memory Management Unit (IOMMU) driver. This flaw allows a malicious guest virtual machine to corrupt hypervisor host memory or cause a denial of service (DoS) by crashing the physical host. The issue occurs because the IOMMU can perform an out-of-bounds read beyond the device table boundary when the table is smaller than its maximum size, allowing a guest that controls adjacent memory to manipulate translation entries.

Statement

This vulnerability is rated as Important because a privileged user inside a guest virtual machine can compromise hypervisor memory or crash the host system, crossing the virtualization trust boundary. Exploitation depends on running virtualization workloads on physical hardware utilizing AMD Zen-family processors. Systems that do not host untrusted virtual machines or that run on non-AMD architectures are not susceptible to this attack.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeChangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.