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(5)

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-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-6.8 (6.8.0-139.139) @ noble2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1067.75) @ noble2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
redhatkernel-0:5.14.0-687.48.1.el9_82026-09-15redhat
redhatkernel-0:4.18.0-553.162.1.el8_102026-09-10redhat
redhatkernel-rt-0:4.18.0-553.162.1.rt7.503.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 22× in last 7d / 100× 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 268 total refreshes for this CVE.

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

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.0% 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