Answer in brief
CVE-2026-64216 records a Unknown severity vulnerability in netfs: Fix potential UAF in netfs_unlock_abandoned_read_pages(). 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 | >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <6080fa3ecfbb4448a3b47368629534c09b6ec750 || >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <3866d015f33aeedf81338dd99154703bef33faef || >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <dbe556972100fabb8e5a1b3d2163831ff07b1e8e | 6080fa3ecfbb4448a3b47368629534c09b6ec750, 3866d015f33aeedf81338dd99154703bef33faef, dbe556972100fabb8e5a1b3d2163831ff07b1e8e |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Jul 24, 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: netfs: Fix potential UAF in netfs_unlock_abandoned_read_pages() netfs_unlock_abandoned_read_pages(rreq) accesses the index of the folios it is wanting to unlock and compares that to rreq->no_unlock_folio so that it doesn't unlock a folio being read for netfs_perform_write() or netfs_write_begin(). However, given that netfs_unlock_abandoned_read_pages() is called _after_ NETFS_RREQ_IN_PROGRESS is cleared, the one folio that it's not allowed to dereference is the one specified by ->no_unlock_folio as ownership immediately reverts to the caller. Fix this by storing the folio pointer instead and using that rather than the index. Also fix netfs_unlock_read_folio() where the same applies.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64216 records a Unknown severity vulnerability in netfs: Fix potential UAF in netfs_unlock_abandoned_read_pages(). 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 | >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <6080fa3ecfbb4448a3b47368629534c09b6ec750 || >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <3866d015f33aeedf81338dd99154703bef33faef || >=ee4cdf7ba857a894ad1650d6ab77669cbbfa329e <dbe556972100fabb8e5a1b3d2163831ff07b1e8e | 6080fa3ecfbb4448a3b47368629534c09b6ec750, 3866d015f33aeedf81338dd99154703bef33faef, dbe556972100fabb8e5a1b3d2163831ff07b1e8e |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Jul 24, 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: netfs: Fix potential UAF in netfs_unlock_abandoned_read_pages() netfs_unlock_abandoned_read_pages(rreq) accesses the index of the folios it is wanting to unlock and compares that to rreq->no_unlock_folio so that it doesn't unlock a folio being read for netfs_perform_write() or netfs_write_begin(). However, given that netfs_unlock_abandoned_read_pages() is called _after_ NETFS_RREQ_IN_PROGRESS is cleared, the one folio that it's not allowed to dereference is the one specified by ->no_unlock_folio as ownership immediately reverts to the caller. Fix this by storing the folio pointer instead and using that rather than the index. Also fix netfs_unlock_read_folio() where the same applies.
Quoted source text, attributed separately from HOL analysis.