CVE-2026-64015

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 — Patch released 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(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
6%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 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(3)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-11ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-11ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-11ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-11ubuntu
ubuntulinux-virtual-6.8 (6.8.0-139.139) @ noble2026-09-11ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-11ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-11ubuntu
redhatkernel-rt-0:4.18.0-553.162.1.rt7.503.el8_102026-09-10redhat
redhatkernel-0:4.18.0-553.162.1.el8_102026-09-10redhat
redhatkernel-0:6.12.0-211.53.1.el10_22026-09-08redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
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 (141 versions)7.0.12-1—

Additional Vendor Advisories

(9)

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 19× in last 7d / 122× 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 244 total refreshes for this CVE.

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

Related CVEs(same vendor)

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 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-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 94.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64015?
CVE-2026-64015 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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