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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Windows Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | — |
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-64015
- https://git.kernel.org/stable/c/43a1e3744548e6fd85873e6fb43e293eb4010694
- https://git.kernel.org/stable/c/4c5d407ba3ff7f30561ff73ba1b07ed70c864edc
- https://git.kernel.org/stable/c/50bb3435a5e627bfbdc52eb4536f49f88b3486b8
- https://git.kernel.org/stable/c/5659e6923cb72f8e18e8b539109ab512455fe195
- https://git.kernel.org/stable/c/66288dcadf80974436250e9f70ed848836b835b5
- https://git.kernel.org/stable/c/cefa4265b11176c897a7d9e8e54d89e3701c5584
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.