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.

Package Linux Kernel
Published 2026-07-19
Last modified 2026-07-19
Patch available
Yes

Affected versions

Fixed in 6.1.175, 6.6.142, 6.12.92, 6.18.34, 7.0.11, 7.1 and their respective stable series.

Fixed in
✓ 6.1.175 6.1.x ✓ 6.6.142 6.6.x ✓ 6.12.92 6.12.x ✓ 6.18.34 6.18.x ✓ 7.0.11 7.0.x ✓ 7.1

Frequently asked questions

  • What is CVE-2026-64015?

    CVE-2026-64015 is a unscored severity Linux kernel vulnerability . CVE-2026-64015 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-64015?

    Yes — CVE-2026-64015 has been patched. Fixed versions include 6.1.175, 6.6.142, 6.12.92 and others.

  • Is CVE-2026-64015 actively exploited?

    No — CVE-2026-64015 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.