In the Linux kernel, the following vulnerability has been resolved: security/keys: fix missed RCU read section on lookup Nicholas Carlini reports… (CVE-2026-64015)
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.
AI Analysis
Technical Summary
The Linux kernel contained a concurrency vulnerability in the security/keys subsystem. Specifically, the keyring code called assoc_array_find() in find_key_to_update() without holding the required RCU read lock. While regular key handling was protected by a keyring semaphore, persistent key handling was not, exposing potential lifetime issues due to improper synchronization. The fix involved implementing the correct RCU read locking to ensure safe access and prevent use-after-free or similar concurrency problems.
Potential Impact
This vulnerability could lead to unsafe memory access or race conditions in the kernel keyring subsystem, potentially causing system instability or security issues related to key management. However, no known exploits are reported in the wild, and the impact is limited to the kernel's key handling internals.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to add the missing RCU read lock in the keyring code. Users should update to a kernel version that includes this fix once available. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: security/keys: fix missed RCU read section on lookup Nicholas Carlini reports… (CVE-2026-64015)
Description
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.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel contained a concurrency vulnerability in the security/keys subsystem. Specifically, the keyring code called assoc_array_find() in find_key_to_update() without holding the required RCU read lock. While regular key handling was protected by a keyring semaphore, persistent key handling was not, exposing potential lifetime issues due to improper synchronization. The fix involved implementing the correct RCU read locking to ensure safe access and prevent use-after-free or similar concurrency problems.
Potential Impact
This vulnerability could lead to unsafe memory access or race conditions in the kernel keyring subsystem, potentially causing system instability or security issues related to key management. However, no known exploits are reported in the wild, and the impact is limited to the kernel's key handling internals.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to add the missing RCU read lock in the keyring code. Users should update to a kernel version that includes this fix once available. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6rrm-p5j2-8pf8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64015"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27aa2a4a8d598912d8a4
Added to database: 07/19/2026, 19:38:18 UTC
Last enriched: 07/19/2026, 19:59:50 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.