CVE-2026-64516

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets

The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access.

Make sure the stack and data offsets are aligned to the 32K TLB size.

Check that the FW microcode actually fits in the space that is reserved for it.

(cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)

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

Published

July 25, 2026

Last Modified

August 5, 2026

Advisory Details (2)

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

drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e5a1d5bb2ff061e64c7992f8e5404dfd4c2d0f3
generic

drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ce0de178ef08408f6ba8f2e9a13bf52fbe5852f4

Vendor Advisories for CVE-2026-64516(1)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-20ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-20ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-20ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-20ubuntu

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 (141 versions)7.0.12-1—

All Vendor Advisories

(4)

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 27× in last 7d / 116× 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 269 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-64516?
CVE-2026-64516 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access.…
When was CVE-2026-64516 disclosed?
CVE-2026-64516 was first published in the National Vulnerability Database on July 25, 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-64516 actively exploited?
CVE-2026-64516 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 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-64516?
CVE-2026-64516 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64516?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64516, 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-64516

Explore →

Is Your Infrastructure Affected by CVE-2026-64516?

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

Start Free Scan →Browse All CVEs