Strix
26.1K

CVE-2026-64015

HIGHCVSS 7.8/10EPSS 0.13%

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.13% 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

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.13%

3.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= b2a4df200d570b2c33a57e1ebfa5896e4bc81b69, < 4c5d407ba3ff7f30561ff73ba1b07ed70c864edc; >= b2a4df200d570b2c33a57e1ebfa5896e4bc81b69, < cefa4265b11176c897a7d9e8e54d89e3701c5584; >= b2a4df200d570b2c33a57e1ebfa5896e4bc81b69, < 5659e6923cb72f8e18e8b539109ab512455fe195; >= b2a4df200d570b2c33a57e1ebfa5896e4bc81b69, < 50bb3435a5e627bfbdc52eb4536f49f88b3486b8; >= b2a4df200d570b2c33a57e1ebfa5896e4bc81b69, < 66288dcadf80974436250e9f70ed848836b835b5; >= b2a4df200d570b2c33a57e1ebfa5896e4bc81b69, < 43a1e3744548e6fd85873e6fb43e293eb4010694
LinuxLinux3.13

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is 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.
How severe is CVE-2026-64015?
CVE-2026-64015 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.13% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64015?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-64015?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST