Memory corruption via persistent-keyring lookup race
Published Jul 19, 2026 · Updated Jul 19, 2026
Race condition in Linux Kernel persistent keyrings allows local users to corrupt kernel memory through concurrent lookup and garbage collection. In find_key_to_update(), assoc_array_find() traverses an associative array without an RCU read lock while assoc_array_gc() removes and later frees its nodes. Persistent-key handling exposes the race to low-privileged local users, and successful triggering can corrupt memory or crash the host.
Summary
What happened
Race condition in Linux Kernel persistent keyrings allows local users to corrupt kernel memory through concurrent lookup and garbage collection. In find_key_to_update(), assoc_array_find() traverses an associative array without an RCU read lock while assoc_array_gc() removes and later frees its nodes. Persistent-key handling exposes the race to low-privileged local users, and successful triggering can corrupt memory or crash the host.
The record
- CVE
- CVE-2026-64015
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.1.175
- Affected versionversion=0 <6.12.92
- Affected versionversion=0 <6.18.34
- Affected versionversion=0 <6.6.142
- Affected versionversion=0 <7.0.11
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <43a1e3744548e6fd85873e6fb43e293eb4010694
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4c5d407ba3ff7f30561ff73ba1b07ed70c864edc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50bb3435a5e627bfbdc52eb4536f49f88b3486b8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5659e6923cb72f8e18e8b539109ab512455fe195
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <66288dcadf80974436250e9f70ed848836b835b5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cefa4265b11176c897a7d9e8e54d89e3701c5584
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo