Public vulnerability disclosure

CVE-2026-99591

iommu/amd: Force device table to maximum size

published

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.

Technical severity7.8 highCVSS 3.1 · CNA: Linux
Published2026-11-20Source updated 2026-11-22
Collected2026-11-223 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ a69ca3401821b7312cb7ec939a8814240fd7b9b3; < e8f1f1ac434f24604d93ea3c8cbac513b2dead69 (affected, git)
≥ a69ca3401821b7312cb7ec939a8814240fd7b9b3; < 046f0b83f18c6313f63419517bb4185e3e0d1a6e (affected, git)
≥ a69ca3401821b7312cb7ec939a8814240fd7b9b3; < bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0 (affected, git)
≥ a69ca3401821b7312cb7ec939a8814240fd7b9b3; < 6e2213dae78b41976c60133eb10cf99e81916638 (affected, git)
Other versions: unaffected
CNA: Linux
Linux
Linux
2.6.27 (affected)
≥ 0; < 2.6.27 (unaffected, semver)
≥ 6.12.118; ≤ 6.12.* (unaffected, semver)
≥ 6.18.64; ≤ 6.18.* (unaffected, semver)
≥ 7.3.5; ≤ 7.3.* (unaffected, semver)
≥ 7.4-rc3; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 7.8
high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HCNA: Linux
3.1 / 7.8
high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HNVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide