CVE-2026-99591: Linux kernel · iommu/amd: Force device table to maximum size
Affects Linux kernelSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · fixed in e8f1f1ac434f24604d93ea3c8cbac513b2dead69 : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:19 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e8f1f1ac434f24604d93ea3c8cbac513b2dead69, bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0, 046f0b83f18c6313f63419517bb4185e3e0d1a6e +4
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/e8f1f1ac434f24604d93ea3c8cbac513b2dead69 (opens in a new tab)
- git.kernel.org/stable/c/046f0b83f18c6313f63419517bb4185e3e0d1a6e (opens in a new tab)
- git.kernel.org/stable/c/bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0 (opens in a new tab)
- git.kernel.org/stable/c/6e2213dae78b41976c60133eb10cf99e81916638 (opens in a new tab)