Answer in brief
CVE-2026-80955 records a High severity (CVSS 7.8) vulnerability in dm-pcache: fix use-after-free and invalid seg operations in kset_replay(). 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.
CVSS is 7.8. 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 | >=1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 <1894fc7a3bab90143dcd26ef8ee27040ef4a7501 || >=1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 <f39a3e9cc5946473e16d6f5071b2ee0216c56d06 || >=1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 <c2e894eac398b258f12fdec73ed6ba081047f7b3 | 1894fc7a3bab90143dcd26ef8ee27040ef4a7501, f39a3e9cc5946473e16d6f5071b2ee0216c56d06, c2e894eac398b258f12fdec73ed6ba081047f7b3 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: dm-pcache: fix use-after-free and invalid seg operations in kset_replay() In kset_replay, when key->seg_gen is stale (key->seg_gen < key->cache_pos.cache_seg->gen), cache_key_put(key) is called but then key->cache_pos.cache_seg is accessed as the argument to cache_seg_get(). This is a use-after-free on the freed key memory. Although mempool recycled memory is not immediately reclaimed or overwritten in practice, this is still a potential UAF bug. Additionally, for expired invalid keys, setting the cache->seg_map bit and calling cache_seg_get() is unreasonable since the corresponding segment data is no longer valid. Fix both issues by moving cache_seg_get() and __set_bit() after the gen check, so they only execute for valid keys, and using continue to skip invalid keys.
Quoted source text, attributed separately from HOL analysis.