iommu/amd: Force device table to maximum size
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e8f1f1ac434f24604d93ea3c8cbac513b2dead69, Kernel 046f0b83f18c6313f63419517bb4185e3e0d1a6e, Kernel 6e2213dae78b41976c60133eb10cf99e81916638 and 4 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e8f1f1ac434f24604d93ea3c8cbac513b2dead69, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <046f0b83f18c6313f63419517bb4185e3e0d1a6e, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e2213dae78b41976c60133eb10cf99e81916638, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0, <6.12.118, <6.18.64, <7.3.5 | e8f1f1ac434f24604d93ea3c8cbac513b2dead69, 046f0b83f18c6313f63419517bb4185e3e0d1a6e, 6e2213dae78b41976c60133eb10cf99e81916638, bdbbf5ad5d032e8cb4b5356d0f3970829f0309c0, 6.12.118, 6.18.64, 7.3.5 |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, <6.12.118 | 6.18.64, 7.3.5, 6.12.118 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket