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
Trending — 4 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
3.1%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 14, 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.

Data Freshness Timeline

(refreshed 12× 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 186 total refreshes for this CVE.

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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs