CVE-2026-99591: iommu/amd: Force device table to maximum size
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 pciseg->devtablesize. A mixed rollout disagrees: the unpatched kernel uses the IVRS-derived size and the patched kernel uses 2MB, so reusedevicetable() 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Configuration
Force the device table size to the maximum 2MB on affected processors.
AMD IOMMU pci_seg->dev_table_size = 2MB - Operational
Update the production kernel and crash kernel together so their device-table sizes match.
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using AMD IOMMUs on CPU families 0x17 (Zen1/Zen2) through 0x1a (Zen5/BRH) are affected. The relevant exposure is in hypervisor-managed device tables, particularly where a guest can influence the condition that causes an out-of-bounds device-table fetch.
What would an attacker need to exploit this?
An attacker would need to be able to act from a guest environment and cause the IOMMU to fetch the device-table entry immediately beyond the allocated table. Exploitation depends on that out-of-bounds entry falling on guest-owned memory, allowing malicious table walks that can corrupt hypervisor pages or crash the system.
What is the mitigation if the kernel update cannot be deployed immediately?
Set the AMD IOMMU device table to the maximum size of 2 MB. The issue does not manifest when the device table is configured at that size.
How can administrators determine whether their configuration needs mitigation?
Check whether the host CPU family is in the 0x17 through 0x1a range and whether its AMD IOMMU device table is smaller than 2 MB. A device table already set to 2 MB is not affected by the described out-of-bounds condition.