CVE-2026-64023

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:

gpio: aggregator: fix a potential use-after-free

On error we free aggr->lookups->dev_id before removing the entry from the lookup table. If a concurrent thread calls gpiod_find() before we remove the entry, it could iterate over the list and call gpiod_match_lookup_table() which unconditionally dereferences dev_id when calling strcmp(). Reverse the order of cleanup.

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
2%
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

gpio: aggregator: fix a potential use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

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

gpio: aggregator: fix a potential use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ac4183a41ba048af89eddd82fe8be64619d0871
generic

gpio: aggregator: fix a potential use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30c073cab97afb31901f94de9605177b6b84367e

Vendor Advisories for CVE-2026-64023(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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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)

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

Frequently asked(5)

What is CVE-2026-64023?
CVE-2026-64023 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: gpio: aggregator: fix a potential use-after-free On error we free aggr->lookups->dev_id before removing the entry from the lookup table. If a concurrent thread calls gpiod_find() before we remove the entry, it could iterate over…
When was CVE-2026-64023 disclosed?
CVE-2026-64023 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-64023 actively exploited?
CVE-2026-64023 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64023?
CVE-2026-64023 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64023?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64023, 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-64023

Explore →

Is Your Infrastructure Affected by CVE-2026-64023?

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

Start Free Scan →Browse All CVEs