CVE-2026-64015

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 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:

security/keys: fix missed RCU read section on lookup

Nicholas Carlini reports that the keyring code calls assoc_array_find() in find_key_to_update() without holding the RCU read lock, while the assoc_array_gc() code really is designed around removing the node from the tree and then freeing it after an RCU grace-period.

The regular key handling doesn't see this because holding the keyring semaphore hides any lifetime issues, but the persistent key handling uses a different model.

Instead of extending the keyring locking, just do the simple RCU locking that the assoc_array was designed for.

CVSS v3
7.8
EG Score
7.8(high)
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

July 20, 2026

Advisory Details (6)

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

security/keys: fix missed RCU read section on lookup - kernel/git/stable/linux.git - Linux kernel stable tree

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

security/keys: fix missed RCU read section on lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66288dcadf80974436250e9f70ed848836b835b5
generic

security/keys: fix missed RCU read section on lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5659e6923cb72f8e18e8b539109ab512455fe195
generic

security/keys: fix missed RCU read section on lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50bb3435a5e627bfbdc52eb4536f49f88b3486b8
generic

security/keys: fix missed RCU read section on lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c5d407ba3ff7f30561ff73ba1b07ed70c864edc
generic

security/keys: fix missed RCU read section on lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43a1e3744548e6fd85873e6fb43e293eb4010694

Vendor Advisories for CVE-2026-64015(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-26ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-26ubuntu

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.

All Vendor Advisories

(2)

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 26× in last 7d / 31× 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.

  1. 2026-07-27 10:24 UTCGHSA enrichment
  2. 2026-07-26 22:40 UTCEG score recompute
  3. 2026-07-26 22:40 UTCVendor advisory
  4. 2026-07-26 22:40 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 10:57 UTCEG score recompute
  8. 2026-07-26 10:57 UTCVendor advisory
  9. 2026-07-26 10:57 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-24 14:18 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 14:18 UTCEPSS rescore
  16. 2026-07-23 03:22 UTCEG score recompute
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-22 14:08 UTCEPSS rescore
  19. 2026-07-21 15:25 UTCEPSS rescore
  20. 2026-07-21 15:25 UTCEPSS rescore
  21. 2026-07-20 17:28 UTCEG score recompute
  22. 2026-07-20 17:28 UTCGHSA enrichment
  23. 2026-07-20 17:08 UTCEPSS rescore
  24. 2026-07-20 14:37 UTCEG score recompute▲ 7.80
  25. 2026-07-20 14:37 UTCGHSA enrichment
Show 6 more
  1. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  2. 2026-07-20 08:34 UTCNVD update
  3. 2026-07-20 07:07 UTCMITRE cvelistV5
  4. 2026-07-19 17:49 UTCNVD update
  5. 2026-07-19 15:46 UTCEG score recompute
  6. 2026-07-19 15:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64015?
CVE-2026-64015 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: security/keys: fix missed RCU read section on lookup Nicholas Carlini reports that the keyring code calls assocarrayfind() in findkeyto_update() without holding the RCU read lock, while the assocarraygc() code really is designed…
When was CVE-2026-64015 disclosed?
CVE-2026-64015 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64015 actively exploited?
CVE-2026-64015 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64015?
CVE-2026-64015 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64015?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64015, 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

Explore the affected products and dependency analysis for CVE-2026-64015

Explore →

Is Your Infrastructure Affected by CVE-2026-64015?

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

Start Free Scan →Browse All CVEs