CVE-2026-64008

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

accel/rocket: fix UAF via dangling GEM handle in create_bo

rocket_ioctl_create_bo() inserts a GEM handle into the file's IDR via drm_gem_handle_create() early on, then performs several operations that can fail (sgt allocation, drm_mm insert, iommu_map). If any fail after the handle is live, the error path calls drm_gem_shmem_object_free() which kfree's the object without removing the handle from the IDR.

This leaves a dangling handle pointing to freed slab memory. Any subsequent ioctl using that handle (PREP_BO, FINI_BO, SUBMIT) calls drm_gem_object_lookup() and dereferences freed memory (UAF).

Fix by moving drm_gem_handle_create() to after all fallible operations succeed, matching the pattern used by panfrost, lima, and etnaviv.

Also fix drm_mm_insert_node_generic() whose return value was silently overwritten by iommu_map_sgtable() on the next line. Add the missing error check.

[tomeu: Move handle creation to the very end]

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

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

accel/rocket: fix UAF via dangling GEM handle in create_bo - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/rocket: fix UAF via dangling GEM handle in create_bo - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/451f1ccbbdb7b65021646704b15902655f8d228a
generic

accel/rocket: fix UAF via dangling GEM handle in create_bo - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18abd88d19ea195e2e1547fca0970c2f91d77a42

Vendor Advisories for CVE-2026-64008(1)

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

Patch Availability(5)

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

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 31× in last 7d / 162× 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 206 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64008?
CVE-2026-64008 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/rocket: fix UAF via dangling GEM handle in create_bo rocketioctlcreate_bo() inserts a GEM handle into the file's IDR via drmgemhandle_create() early on, then performs several operations that can fail (sgt allocation, drmmm…
When was CVE-2026-64008 disclosed?
CVE-2026-64008 was first published in the National Vulnerability Database on July 19, 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-64008 actively exploited?
CVE-2026-64008 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64008?
CVE-2026-64008 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64008?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64008, 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-64008

Explore →

Is Your Infrastructure Affected by CVE-2026-64008?

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