CVE-2026-46218

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: Add bounds checking to ib_{get,set}_value

The uvd/vce/vcn code accesses the IB at predefined offsets without checking that the IB is large enough. Check the bounds here. The caller is responsible for making sure it can handle arbitrary return values.

Also make the idx a uint32_t to prevent overflows causing the condition to fail.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Jun 11, 2026
No patch confirmed yet.
generic

drm/amdgpu: Add bounds checking to ib_{get,set}_value - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: Add bounds checking to ib_{get,set}_value - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: Add bounds checking to ib_{get,set}_value - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: Add bounds checking to ib_{get,set}_value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66085e206431ef88ce36f53c1f53d570790ccc9e
generic

drm/amdgpu: Add bounds checking to ib_{get,set}_value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5da6c6430be0acb25b4242bce0323fc514d4e3cf
generic

drm/amdgpu: Add bounds checking to ib_{get,set}_value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fb5cb556b249b2b64c0f818136c4c3e838ef53f

Vendor Advisories for CVE-2026-46218(2)

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

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-136.136.2~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.90-1~bpo12+1 (23 versions)6.12.90-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (135 versions)7.0.9-1

Additional Vendor Advisories

(22)

Data Freshness Timeline

(refreshed 4× in last 7d / 86× 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 276 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46218?
CVE-2026-46218 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Add bounds checking to ib{get,set}value The uvd/vce/vcn code accesses the IB at predefined offsets without checking that the IB is large enough. Check the bounds here. The caller is responsible for making sure it can…
When was CVE-2026-46218 disclosed?
CVE-2026-46218 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46218 actively exploited?
CVE-2026-46218 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-46218?
CVE-2026-46218 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46218, 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-46218

Explore →

Is Your Infrastructure Affected by CVE-2026-46218?

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