CVE-2026-64015
Last modified
CVE-2026-64015 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.13, < 6.1.175 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.142 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.92 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.34 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-64015?
How severe is CVE-2026-64015?
How do I fix CVE-2026-64015?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-6401The Bottom Bar plugin for WordPress is vulnerable to Cross-S…4.3
- CVE-2026-64010In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64011In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64012In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64013In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64014In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64016In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64017In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64018In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-64019In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6402webpack-dev-server versions up to and including 5.2.3 are vu…6.5
- CVE-2026-64020In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2026-64015?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
