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.

CVSS 3.1

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

EPSS

0.2% chance of exploitation in the next 30 days; higher than 4% of CVEs (scores of 2026-10-25)

CWEs

CWE-125, CWE-362

Published

2026-07-19

Modified

2026-10-19

Record from

the NVD, synced 2026-10-21

Affected

• linux:linux_kernel

References

• https://git.kernel.org/stable/c/43a1e3744548e6fd85873e6fb43e293eb4010694
• https://git.kernel.org/stable/c/4c5d407ba3ff7f30561ff73ba1b07ed70c864edc
• https://git.kernel.org/stable/c/50bb3435a5e627bfbdc52eb4536f49f88b3486b8
• https://git.kernel.org/stable/c/5659e6923cb72f8e18e8b539109ab512455fe195
• https://git.kernel.org/stable/c/66288dcadf80974436250e9f70ed848836b835b5

Check your stackJSON