# CVE-2026-53283: linux: In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Bounds-check devid in __rlookup_amd_i... CVE-2026-53283 is fixed in 19 products on 1 platform, first by ALAS2023-2026-1866, released June 22, 2026. It is not reported as exploited. Patch Radar priority: Routine. - Web page: https://patchblox.com/security/cve/CVE-2026-53283 - Priority: Routine - CVSS: 5.5 (medium) - EPSS: 0.0016 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Jun 22, 2026 ## Description In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Bounds-check devid in __rlookup_amd_iommu() iommu_device_register() walks every device on the PCI bus via bus_for_each_dev() and calls amd_iommu_probe_device() for each. The inlined check_device() path computes the device's sbdf, calls rlookup_amd_iommu() to find the owning IOMMU, and only afterwards verifies devid <= pci_seg->last_bdf. __rlookup_amd_iommu() indexes rlookup_table[devid] with no bounds check of its own, so for a PCI device whose BDF is not described by the IVRS, the lookup reads past the end of the allocation before the caller's bounds check can run. This was harmless before commit e874c666b15b ("iommu/amd: Change rlookup, irq_lookup, and alias to use kvalloc()"): the table was a zeroed page-order allocation, so the over-read returned NULL and the caller's NULL check skipped the device. After that commit the table is a tight kvcalloc() and the over-read returns adjacent slab contents, which check_device() then dereferences as a struct amd_iommu *, causing a boot-time GPF. Seen on Google Compute Engine ct6e VMs, where the virtualized IVRS describes only the four TPU endpoints 00:04.0-07.0; the gVNIC at 00:08.0 (devid 0x40) indexes 56 bytes past the 456-byte allocation, into the adjacent kmalloc-512 slab object: pci 0000:00:04.0: Adding to iommu group 0 pci 0000:00:05.0: Adding to iommu group 1 pci 0000:00:06.0: Adding to iommu group 2 pci 0000:00:07.0: Adding to iommu group 3 Oops: general protection fault, probably for non-canonical address 0x3a64695f78746382: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.22 #1 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/06/2025 RIP: 0010:amd_iommu_probe_device+0x54/0x3a0 Call Trace: __iommu_probe_device+0x107/0x520 probe_iommu_group+0x29/0x50 bus_for_each_dev+0x7e/0xe0 iommu_device_register+0xc9/0x240 iommu_go_to_state+0x9c0/0x1c60 amd_iommu_init+0x14/0x40 pci_iommu_init+0x16/0x60 do_one_initcall+0x47/0x2f0 Guard the array access in __rlookup_amd_iommu(). With the fix applied on 6.18.22, the gVNIC at 00:08.0 is skipped cleanly and the VM boots. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel-livepatch-6.18.33-63.124 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | linux Debian 14 | 7.0.10-1 | [DEBIAN-CVE-2026-53283](https://patchblox.com/security/data/fix/linux/debian-cve-2026-53283.md) | Jun 27, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | --- Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.