# CVE-2026-99591: iommu/amd: Force device table to maximum size

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ a69ca3401821b7312cb7ec939a8814240fd7b9b3; < e8f1f1ac434f24604d93ea3c8cbac513b2dead69 (affected, git); ≥ a69ca3401821b7312cb7ec939a8814240fd7b9b3; < 046f0b83f18c6313f63419517bb4185e3e0d1a6e (affected, git); ≥ a69ca3401821b7312cb7ec939a8814240fd7b9b3; < bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0 (affected, git); ≥ a69ca3401821b7312cb7ec939a8814240fd7b9b3; < 6e2213dae78b41976c60133eb10cf99e81916638 (affected, git). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.19%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

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

## References

- https://git.kernel.org/stable/c/e8f1f1ac434f24604d93ea3c8cbac513b2dead69 (CNA: Linux)

- https://git.kernel.org/stable/c/046f0b83f18c6313f63419517bb4185e3e0d1a6e (CNA: Linux)

- https://git.kernel.org/stable/c/bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0 (CNA: Linux)

- https://git.kernel.org/stable/c/6e2213dae78b41976c60133eb10cf99e81916638 (CNA: Linux)

- https://git.kernel.org/stable/c/046f0b83f18c6313f63419517bb4185e3e0d1a6e (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/6e2213dae78b41976c60133eb10cf99e81916638 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/e8f1f1ac434f24604d93ea3c8cbac513b2dead69 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99591; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99591; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99591; retrieved 2026-11-22; source updated Not reported

Revision: bc1ab8f46c4ae0b7b97d54a4085891a0ca977e2f96342f3b8013cedad5d3ff30

Canonical: https://y2.dev/cve/CVE-2026-99591

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.