Disclosure summary
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.
Source-reported weakness categories
CWE-125
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
NIST National Vulnerability Database · NVD-CVE-2026-64015
Open original source · Updated Oct 08, 2026
Only CPE matches marked vulnerable=true are indexed. AND/OR platform conditions must be checked in the original NVD record.
| Vendor | Product / association | Version / bounds |
|---|---|---|
| linux | linux_kernel | * {"versionStartIncluding":"6.19","versionEndExcluding":"7.0.11"} |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
Original records & references
- NIST NVD record
- CVE Program record
- git.kernel.org — Patch
- git.kernel.org — Patch
- git.kernel.org — Patch
- git.kernel.org — Patch
- git.kernel.org — Patch
- git.kernel.org — Patch
PUBLISHED 2026-07-19T12:17:41-04:00
MODIFIED 2026-10-08T13:09:49-04:00
INGESTED 2026-10-10T20:50:36-04:00