CVE-2026-53283

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 8, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

iommu/amd: Bounds-check devid in __rlookup_amd_iommu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f0a0f01787ecece814414b0665df879b69849d09
generic

iommu/amd: Bounds-check devid in __rlookup_amd_iommu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79db4cbab81f07ce69a93d379ebd40d3709ecfb2
generic

iommu/amd: Bounds-check devid in __rlookup_amd_iommu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07d0f496fe7ec5abe3bee7e38be709521567bb33

Vendor Advisories for CVE-2026-53283(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-06ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-06ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-06ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-06ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-06ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-06ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-06ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-06ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:58 UTCEG score recompute
  6. 2026-09-06 14:58 UTCVendor advisory
  7. 2026-09-06 14:58 UTCGHSA enrichment
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:12 UTCEPSS rescore
  11. 2026-09-01 13:54 UTCEPSS rescore
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-08-30 19:18 UTCEG score recompute
  14. 2026-08-30 19:18 UTCVendor advisory
  15. 2026-08-30 19:18 UTCGHSA enrichment
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 22:58 UTCEG score recompute
  20. 2026-08-27 22:58 UTCVendor advisory
  21. 2026-08-27 22:58 UTCGHSA enrichment
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 05:07 UTCEG score recompute
Show 75 more
  1. 2026-08-25 05:07 UTCVendor advisory
  2. 2026-08-25 05:06 UTCGHSA enrichment
  3. 2026-08-24 06:45 UTCVendor advisory
  4. 2026-08-24 06:45 UTCGHSA enrichment
  5. 2026-08-23 07:45 UTCEG score recompute
  6. 2026-08-23 07:45 UTCVendor advisory
  7. 2026-08-23 07:45 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 09:23 UTCEG score recompute
  10. 2026-08-22 09:23 UTCVendor advisory
  11. 2026-08-22 09:23 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 05:08 UTCEG score recompute
  14. 2026-08-21 05:08 UTCVendor advisory
  15. 2026-08-21 05:08 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 06:41 UTCEG score recompute
  18. 2026-08-20 06:41 UTCVendor advisory
  19. 2026-08-20 06:41 UTCGHSA enrichment
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 23:41 UTCEG score recompute
  22. 2026-08-18 23:41 UTCVendor advisory
  23. 2026-08-18 23:41 UTCGHSA enrichment
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 13:47 UTCEPSS rescore
  26. 2026-08-17 11:49 UTCEG score recompute
  27. 2026-08-17 11:49 UTCVendor advisory
  28. 2026-08-17 11:49 UTCGHSA enrichment
  29. 2026-08-16 14:56 UTCEPSS rescore
  30. 2026-08-16 13:26 UTCEG score recompute
  31. 2026-08-16 13:26 UTCVendor advisory
  32. 2026-08-16 13:26 UTCGHSA enrichment
  33. 2026-08-16 02:14 UTCEPSS rescore
  34. 2026-08-15 15:05 UTCEG score recompute
  35. 2026-08-15 15:05 UTCVendor advisory
  36. 2026-08-15 15:05 UTCGHSA enrichment
  37. 2026-08-15 01:30 UTCEPSS rescore
  38. 2026-08-14 16:43 UTCEG score recompute
  39. 2026-08-14 16:43 UTCVendor advisory
  40. 2026-08-14 16:43 UTCGHSA enrichment
  41. 2026-08-13 22:00 UTCEPSS rescore
  42. 2026-08-13 18:22 UTCVendor advisory
  43. 2026-08-13 18:22 UTCGHSA enrichment
  44. 2026-08-12 19:06 UTCEG score recompute
  45. 2026-08-12 19:06 UTCVendor advisory
  46. 2026-08-12 19:06 UTCGHSA enrichment
  47. 2026-08-12 13:51 UTCEPSS rescore
  48. 2026-08-11 20:45 UTCEG score recompute
  49. 2026-08-11 20:45 UTCVendor advisory
  50. 2026-08-11 20:45 UTCGHSA enrichment
  51. 2026-08-11 00:00 UTCEPSS rescore
  52. 2026-08-10 22:24 UTCVendor advisory
  53. 2026-08-10 22:24 UTCGHSA enrichment
  54. 2026-08-10 00:01 UTCEG score recompute
  55. 2026-08-10 00:01 UTCVendor advisory
  56. 2026-08-10 00:01 UTCGHSA enrichment
  57. 2026-08-09 13:46 UTCEPSS rescore
  58. 2026-08-09 01:40 UTCEG score recompute
  59. 2026-08-09 01:40 UTCVendor advisory
  60. 2026-08-09 01:40 UTCGHSA enrichment
  61. 2026-08-08 16:37 UTCEPSS rescore
  62. 2026-08-08 03:19 UTCEG score recompute
  63. 2026-08-08 03:19 UTCVendor advisory
  64. 2026-08-08 03:19 UTCGHSA enrichment
  65. 2026-08-07 04:58 UTCEG score recompute
  66. 2026-08-07 04:58 UTCVendor advisory
  67. 2026-08-07 04:58 UTCGHSA enrichment
  68. 2026-08-06 13:47 UTCEPSS rescore
  69. 2026-08-06 06:37 UTCEG score recompute
  70. 2026-08-06 06:37 UTCVendor advisory
  71. 2026-08-06 06:37 UTCGHSA enrichment
  72. 2026-08-05 19:17 UTCEPSS rescore
  73. 2026-08-05 08:16 UTCEG score recompute
  74. 2026-08-05 08:16 UTCGHSA enrichment
  75. 2026-08-04 15:10 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53283?
CVE-2026-53283 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Bounds-check devid in rlookupamdiommu() iommudeviceregister() walks every device on the PCI bus via busforeachdev() and calls amdiommuprobedevice() for each. The inlined check_device() path computes the device's sbdf,…
When was CVE-2026-53283 disclosed?
CVE-2026-53283 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53283 actively exploited?
CVE-2026-53283 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53283?
CVE-2026-53283 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53283?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53283, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53283

Explore →

Is Your Infrastructure Affected by CVE-2026-53283?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs