Answer in brief
CVE-2026-80962 records a Unknown severity vulnerability in dm-pcache: validate geometry fields from on-disk cache_info. 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 | >=1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 <ab5dcde6fa96bc115b85f3621c60e39c66229a90 || >=1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 <3e19172089ec81132a8a48e802b1034a744209f4 || >=1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 <32d1809da31094ef76fd98dc1f1a8b55ca1295dd | ab5dcde6fa96bc115b85f3621c60e39c66229a90, 3e19172089ec81132a8a48e802b1034a744209f4, 32d1809da31094ef76fd98dc1f1a8b55ca1295dd |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 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: validate geometry fields from on-disk cache_info cache_segs_init() iterates cache_info->n_segs times indexing cache->segments[], which is sized to the cache device geometry, and get_seg_id() takes each segment id from the on-media cache_info and the per-segment next_seg link. Both come from cache device metadata that is only CRC-protected with a fixed public seed, so whoever supplies the cache device on a table load (CAP_SYS_ADMIN) controls them: an oversized n_segs or an out-of-range id drives an out-of-bounds access of cache->segments[] and a wild CACHE_DEV_SEGMENT() pointer into the device mapping -- an out-of-bounds read and write from on-disk data. Reject an n_segs that exceeds the device segment count and a segment id that is out of range before either is used. Valid metadata is unaffected.
Quoted source text, attributed separately from HOL analysis.