CVE-2026-64219

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 0

A fix is available — apply it.

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

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async

[Why&How] dc_process_dmub_aux_transfer_async() copies payload->length bytes into a 16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which is a no-op in release builds. If a caller ever passes length > 16 this results in a stack buffer overflow via memcpy.

Additionally, link_index is used to dereference dc->links[] without bounds checking against dc->link_count, risking an out-of-bounds access.

Replace the ASSERT with a hard runtime check that returns false when payload->length exceeds the destination buffer size, and add a bounds check for link_index before it is used.

(cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)

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

Published

July 24, 2026

Last Modified

August 11, 2026

Advisory Details (7)

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

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90c398e822ca76e40548df0c061dd4f93ea92d71
generic

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c92f6d9600efa3ef0d9e560a2b52776d9803c29
generic

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3265f3ed373fb8048be713aadcdf702579a0e53d
generic

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ecde19bfce6535bffddad1139ff466b6d401b8e
generic

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c8c6e912f2945b2a3e669afca6b52174b88e86e
generic

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16a5fa57565afb6bf37e18129921c270c93d8e2b

Vendor Advisories for CVE-2026-64219(3)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-30ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-30ubuntu
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-0:4.18.0-553.156.1.el8_102026-08-17redhat
redhatkernel-rt-0:4.18.0-553.156.1.rt7.497.el8_102026-08-17redhat

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

(3 across 3 ecosystems)
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.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 33× in last 7d / 172× 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 203 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64219?
CVE-2026-64219 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate payload length and linkindex in dcprocessdmubauxtransferasync [Why&How] dcprocessdmubauxtransfer_async() copies payload->length bytes into a 16-byte stack buffer (dpaux.data[16]) guarded only by an…
When was CVE-2026-64219 disclosed?
CVE-2026-64219 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64219 actively exploited?
CVE-2026-64219 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 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64219?
CVE-2026-64219 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-64219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64219, 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-64219

Explore →

Is Your Infrastructure Affected by CVE-2026-64219?

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

Start Free Scan →Browse All CVEs