Answer in brief
CVE-2024-26630 records a High severity (CVSS 7.1) vulnerability in mm: cachestat: fix folio read-after-free in cache walk. 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.1. 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 | >=cf264e1329fb0307e044f7675849f9f38b44c11a <ba60fdf75e89ea762bb617be578dc47f27655117 || >=cf264e1329fb0307e044f7675849f9f38b44c11a <fe7e008e0ce728252e4ec652cceebcc62211657c || >=cf264e1329fb0307e044f7675849f9f38b44c11a <3a75cb05d53f4a6823a32deb078de1366954a804 | ba60fdf75e89ea762bb617be578dc47f27655117, fe7e008e0ce728252e4ec652cceebcc62211657c, 3a75cb05d53f4a6823a32deb078de1366954a804 |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
Mar 13, 2024
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: mm: cachestat: fix folio read-after-free in cache walk In cachestat, we access the folio from the page cache's xarray to compute its page offset, and check for its dirty and writeback flags. However, we do not hold a reference to the folio before performing these actions, which means the folio can concurrently be released and reused as another folio/page/slab. Get around this altogether by just using xarray's existing machinery for the folio page offsets and dirty/writeback states. This changes behavior for tmpfs files to now always report zeroes in their dirty and writeback counters. This is okay as tmpfs doesn't follow conventional writeback cache behavior: its pages get "cleaned" during swapout, after which they're no longer resident etc.
Quoted source text, attributed separately from HOL analysis.