Skip to content
Threat Brief

← All advisories

CVE-2026-99591

Severity unknownNo known exploitationFix available

iommu/amd: Force device table to maximum size

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Force device table to maximum size IOMMU can perform out-of-bounds read of the device table entry (DTE) that is adjacent to the last DTE and falls outside the device table. For example, if the device table can hold 0 to N-1 entries, then the IOMMU can be made to fetch the Nth entry, which falls outside the device table. The device table is owned by the hypervisor (HV) and is assigned in 4KB pages that are contiguous in system physical address (SPA). If the out-of-bound DTE falls on a guest-owned page, then the guest can exploit this bug to setup malicious table walks to corrupt HV pages and/or bring down the system. Note that this bug does not manifest when the device table size is set to its maximum size of 2MB. Therefore, force the device table size to the maximum 2MB on affected processors. These are CPU family 0x17 (Zen1/Zen2) through family 0x1a (Zen5/BRH). This is a mitigation for CVE-2024-21963. kdump reuses the previous kernel's device table only when the size encoded in the IOMMU device-table register matches pci_seg->dev_table_size. A mixed rollout disagrees: the unpatched kernel uses the IVRS-derived size and the patched kernel uses 2MB, so __reuse_device_table() rejects the table. On SNP-capable IOMMUs that rejection panics the kdump kernel. Kernels that both have this patch agree on 2MB and reuse succeeds. Update the production kernel and the crash kernel together.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before e8f1f1ac434f24604d93ea3c8cbac513b2dead69e8f1f1ac434f24604d93ea3c8cbac513b2dead69CVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 046f0b83f18c6313f63419517bb4185e3e0d1a6e046f0b83f18c6313f63419517bb4185e3e0d1a6eCVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0CVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 6e2213dae78b41976c60133eb10cf99e819166386e2213dae78b41976c60133eb10cf99e81916638CVE Program
LinuxLinuxall versions before 6.12.1186.12.118CVE Program
LinuxLinuxall versions before 6.18.646.18.64CVE Program
LinuxLinuxall versions before 7.3.57.3.5CVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc3Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references