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-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-15ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-15ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-15ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-15ubuntu

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 29× in last 7d / 123× 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 249 total refreshes for this CVE.

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

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.5% 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