Answer in brief
CVE-2025-21893 records a Unknown severity vulnerability in keys: Fix UAF in key_put(). 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 | >=9578e327b2b4935a25d49e3891b8fcca9b6c10c6 <6afe2ea2daec156bd94ad2c5a6f4f4c48240dcd3 || >=9578e327b2b4935a25d49e3891b8fcca9b6c10c6 <f6a3cf833188e897c97028cd7b926e3f2cb1a8c0 || >=9578e327b2b4935a25d49e3891b8fcca9b6c10c6 <75845c6c1a64483e9985302793dbf0dfa5f71e32 | 6afe2ea2daec156bd94ad2c5a6f4f4c48240dcd3, f6a3cf833188e897c97028cd7b926e3f2cb1a8c0, 75845c6c1a64483e9985302793dbf0dfa5f71e32 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Mar 31, 2025
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: keys: Fix UAF in key_put() Once a key's reference count has been reduced to 0, the garbage collector thread may destroy it at any time and so key_put() is not allowed to touch the key after that point. The most key_put() is normally allowed to do is to touch key_gc_work as that's a static global variable. However, in an effort to speed up the reclamation of quota, this is now done in key_put() once the key's usage is reduced to 0 - but now the code is looking at the key after the deadline, which is forbidden. Fix this by using a flag to indicate that a key can be gc'd now rather than looking at the key's refcount in the garbage collector.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-21893 records a Unknown severity vulnerability in keys: Fix UAF in key_put(). 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 | >=9578e327b2b4935a25d49e3891b8fcca9b6c10c6 <6afe2ea2daec156bd94ad2c5a6f4f4c48240dcd3 || >=9578e327b2b4935a25d49e3891b8fcca9b6c10c6 <f6a3cf833188e897c97028cd7b926e3f2cb1a8c0 || >=9578e327b2b4935a25d49e3891b8fcca9b6c10c6 <75845c6c1a64483e9985302793dbf0dfa5f71e32 | 6afe2ea2daec156bd94ad2c5a6f4f4c48240dcd3, f6a3cf833188e897c97028cd7b926e3f2cb1a8c0, 75845c6c1a64483e9985302793dbf0dfa5f71e32 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Mar 31, 2025
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: keys: Fix UAF in key_put() Once a key's reference count has been reduced to 0, the garbage collector thread may destroy it at any time and so key_put() is not allowed to touch the key after that point. The most key_put() is normally allowed to do is to touch key_gc_work as that's a static global variable. However, in an effort to speed up the reclamation of quota, this is now done in key_put() once the key's usage is reduced to 0 - but now the code is looking at the key after the deadline, which is forbidden. Fix this by using a flag to indicate that a key can be gc'd now rather than looking at the key's refcount in the garbage collector.
Quoted source text, attributed separately from HOL analysis.