Answer in brief
CVE-2026-64015 records a Unknown severity vulnerability in security/keys: fix missed RCU read section on lookup. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <4c5d407ba3ff7f30561ff73ba1b07ed70c864edc || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <cefa4265b11176c897a7d9e8e54d89e3701c5584 || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <5659e6923cb72f8e18e8b539109ab512455fe195 || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <50bb3435a5e627bfbdc52eb4536f49f88b3486b8 || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <66288dcadf80974436250e9f70ed848836b835b5 || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <43a1e3744548e6fd85873e6fb43e293eb4010694 | 4c5d407ba3ff7f30561ff73ba1b07ed70c864edc, cefa4265b11176c897a7d9e8e54d89e3701c5584, 5659e6923cb72f8e18e8b539109ab512455fe195, 50bb3435a5e627bfbdc52eb4536f49f88b3486b8, 66288dcadf80974436250e9f70ed848836b835b5, 43a1e3744548e6fd85873e6fb43e293eb4010694 |
| Linux/Linuxgeneric | 3.13 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64015 records a Unknown severity vulnerability in security/keys: fix missed RCU read section on lookup. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <4c5d407ba3ff7f30561ff73ba1b07ed70c864edc || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <cefa4265b11176c897a7d9e8e54d89e3701c5584 || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <5659e6923cb72f8e18e8b539109ab512455fe195 || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <50bb3435a5e627bfbdc52eb4536f49f88b3486b8 || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <66288dcadf80974436250e9f70ed848836b835b5 || >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <43a1e3744548e6fd85873e6fb43e293eb4010694 | 4c5d407ba3ff7f30561ff73ba1b07ed70c864edc, cefa4265b11176c897a7d9e8e54d89e3701c5584, 5659e6923cb72f8e18e8b539109ab512455fe195, 50bb3435a5e627bfbdc52eb4536f49f88b3486b8, 66288dcadf80974436250e9f70ed848836b835b5, 43a1e3744548e6fd85873e6fb43e293eb4010694 |
| Linux/Linuxgeneric | 3.13 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.