{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99591","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.423Z","datePublished":"2026-11-20T05:49:19.670Z","dateUpdated":"2026-11-22T11:09:09.689Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-22T11:09:09.689Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Force device table to maximum size\n\nIOMMU can perform out-of-bounds read of the device table entry (DTE)\nthat is adjacent to the last DTE and falls outside the device table.\nFor example, if the device table can hold 0 to N-1 entries, then the\nIOMMU can be made to fetch the Nth entry, which falls outside the\ndevice table.\n\nThe device table is owned by the hypervisor (HV) and is assigned in 4KB\npages that are contiguous in system physical address (SPA). If the\nout-of-bound DTE falls on a guest-owned page, then the guest can exploit\nthis bug to setup malicious table walks to corrupt HV pages and/or bring\ndown the system. Note that this bug does not manifest when the device\ntable size is set to its maximum size of 2MB.\n\nTherefore, force the device table size to the maximum 2MB on affected\nprocessors. These are CPU family 0x17 (Zen1/Zen2) through family 0x1a\n(Zen5/BRH).\n\nThis is a mitigation for CVE-2024-21963.\n\nkdump reuses the previous kernel's device table only when the size\nencoded in the IOMMU device-table register matches\npci_seg->dev_table_size. A mixed rollout disagrees: the unpatched\nkernel uses the IVRS-derived size and the patched kernel uses 2MB,\nso __reuse_device_table() rejects the table. On SNP-capable IOMMUs\nthat rejection panics the kdump kernel. Kernels that both have this\npatch agree on 2MB and reuse succeeds. Update the production kernel\nand the crash kernel together."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - init_iommu_one() reaches alloc_pci_segment() through get_pci_segment() during IVRS setup. alloc_pci_segment() sets dev_table_size from find_last_devid_acpi(), and the IOMMU reads one dev_table_entry past that iommu_alloc_pages_sz() buffer from the guest page at the next SPA.\nAC:H - The IOMMU reads that slot only for requester ID dev_table_size/32, past last_bdf, and only if the page after alloc_dev_table()'s boot-time GFP_DMA32 allocation is guest-owned. check_device() will not install that ID. The guest cannot move the boot allocation or choose the SPA that follows it.\nPR:L - The forged entry is written by a guest tenant. init_iommu_one() publishes the short table at boot, and the IOMMU consumes the adjacent page with no host credential check. Guest kernel control is low privilege on the host, not init-namespace root.\nUI:N - The guest writes the dev_table_entry image into a page it already owns. No host operator has to mount an image, attach media, or confirm a prompt.\nS:C - alloc_dev_table() keeps the device table as hypervisor memory. The IOMMU treats the guest page past it as a DTE and walks DTE_HOST_TRP for DMA, so the guest corrupts HV pages across the guest-to-host boundary.\nC:H - That out-of-bounds dev_table_entry is honored with DTE_FLAG_IR and DTE_HOST_TRP, so device DMA reads follow guest-built page tables into hypervisor SPAs and return host memory to the device.\nI:H - DTE_FLAG_IW in the same forged entry makes those walks writable, and the guest picks the SPA the device stores to. The fix commit describes the result as malicious table walks that corrupt HV pages.\nA:H - A malicious walk or the HV corruption it causes brings the host down. The fix commit states that fetching the entry past the programmed device table can bring down the system."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iommu/amd/init.c"],"versions":[{"version":"a69ca3401821b7312cb7ec939a8814240fd7b9b3","lessThan":"e8f1f1ac434f24604d93ea3c8cbac513b2dead69","status":"affected","versionType":"git"},{"version":"a69ca3401821b7312cb7ec939a8814240fd7b9b3","lessThan":"046f0b83f18c6313f63419517bb4185e3e0d1a6e","status":"affected","versionType":"git"},{"version":"a69ca3401821b7312cb7ec939a8814240fd7b9b3","lessThan":"bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0","status":"affected","versionType":"git"},{"version":"a69ca3401821b7312cb7ec939a8814240fd7b9b3","lessThan":"6e2213dae78b41976c60133eb10cf99e81916638","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iommu/amd/init.c"],"versions":[{"version":"2.6.27","status":"affected"},{"version":"0","lessThan":"2.6.27","status":"unaffected","versionType":"semver"},{"version":"6.12.118","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.64","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.5","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc3","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.27","versionEndExcluding":"6.12.118"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.27","versionEndExcluding":"6.18.64"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.27","versionEndExcluding":"7.3.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.27","versionEndExcluding":"7.4-rc3"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/e8f1f1ac434f24604d93ea3c8cbac513b2dead69"},{"url":"https://git.kernel.org/stable/c/046f0b83f18c6313f63419517bb4185e3e0d1a6e"},{"url":"https://git.kernel.org/stable/c/bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0"},{"url":"https://git.kernel.org/stable/c/6e2213dae78b41976c60133eb10cf99e81916638"}],"title":"iommu/amd: Force device table to maximum size","x_generator":{"engine":"bippy-1.2.0"}}}}