CVE-2026-64015security/keys: fix missed RCU read section on lookup
- 7.8HighCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 95% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 – < 1d8d987a2aacde238ecd0f4946f28cef74c42b79
- affected b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 – < 5036a9aa7f21fbce89a2a8451bbc177bae2e920d
- affected b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 – < 4c5d407ba3ff7f30561ff73ba1b07ed70c864edc
- affected b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 – < cefa4265b11176c897a7d9e8e54d89e3701c5584
- affected b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 – < 5659e6923cb72f8e18e8b539109ab512455fe195
- affected b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 – < 50bb3435a5e627bfbdc52eb4536f49f88b3486b8
- affected b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 – < 66288dcadf80974436250e9f70ed848836b835b5
- affected b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 – < 43a1e3744548e6fd85873e6fb43e293eb4010694
- affected 3.13
- unaffected < 3.13
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.142 – ≤ 6.6.*
- unaffected 6.12.92 – ≤ 6.12.*
- unaffected 6.18.34 – ≤ 6.18.*
- unaffected 7.0.11 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References8
- https://git.kernel.org/stable/c/1d8d987a2aacde238ecd0f4946f28cef74c42b79 (opens in a new tab)
- https://git.kernel.org/stable/c/5036a9aa7f21fbce89a2a8451bbc177bae2e920d (opens in a new tab)
- https://git.kernel.org/stable/c/4c5d407ba3ff7f30561ff73ba1b07ed70c864edc (opens in a new tab)
- https://git.kernel.org/stable/c/cefa4265b11176c897a7d9e8e54d89e3701c5584 (opens in a new tab)
- https://git.kernel.org/stable/c/5659e6923cb72f8e18e8b539109ab512455fe195 (opens in a new tab)
- https://git.kernel.org/stable/c/50bb3435a5e627bfbdc52eb4536f49f88b3486b8 (opens in a new tab)
- https://git.kernel.org/stable/c/66288dcadf80974436250e9f70ed848836b835b5 (opens in a new tab)
- https://git.kernel.org/stable/c/43a1e3744548e6fd85873e6fb43e293eb4010694 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-45588 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64015)Record last updated .