Answer in brief
CVE-2026-64031 records a High severity (CVSS 7.8) vulnerability in erofs: fix managed cache race for unaligned extents. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7361d1e3763baaf7b9349c576137851458ad38d1 <425d32d6288d7d845e486af9419bbedccd8c9103 || >=7361d1e3763baaf7b9349c576137851458ad38d1 <038166f873c4caf6e85cfd4ea0c5a5ba297b4e8b || >=7361d1e3763baaf7b9349c576137851458ad38d1 <649932fc3815eda2f24eb4de4b3a5e94886ee0b9 | 425d32d6288d7d845e486af9419bbedccd8c9103, 038166f873c4caf6e85cfd4ea0c5a5ba297b4e8b, 649932fc3815eda2f24eb4de4b3a5e94886ee0b9 |
| Linux/Linuxgeneric | 6.15 | Not reported |
| Linux/Linuxgeneric | >=722f0fcdb0bb7d12a5c6d9460b9a7de1f735f36d <2718cdb6db0fdbe375e61f2980aada27bafb323e || >=7361d1e3763baaf7b9349c576137851458ad38d1 <425d32d6288d7d845e486af9419bbedccd8c9103 || >=7361d1e3763baaf7b9349c576137851458ad38d1 <038166f873c4caf6e85cfd4ea0c5a5ba297b4e8b || >=7361d1e3763baaf7b9349c576137851458ad38d1 <649932fc3815eda2f24eb4de4b3a5e94886ee0b9 | 2718cdb6db0fdbe375e61f2980aada27bafb323e, 425d32d6288d7d845e486af9419bbedccd8c9103, 038166f873c4caf6e85cfd4ea0c5a5ba297b4e8b, 649932fc3815eda2f24eb4de4b3a5e94886ee0b9 |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 13, 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: erofs: fix managed cache race for unaligned extents After unaligned compressed extents were introduced, the following race could occur: [Thread 1] [Thread 2] (z_erofs_fill_bio_vec) <handle a Z_EROFS_PREALLOCATED_FOLIO folio> ... filemap_add_folio (1) (z_erofs_bind_cache) <the same folio is found..> .. .. folio_attach_private (2) filemap_add_folio (3) again Since (1) is executed but (2) hasn't been executed yet, it's possible that another thread finds the same managed folio in z_erofs_bind_cache() for a different pcluster and calls filemap_add_folio() again since folio->private is still Z_EROFS_PREALLOCATED_FOLIO. Fix this by explicitly clearing folio->private before making the folio visible in the managed cache so that another pcluster can simply wait on the locked managed folio as what we did for other shared cases [1]. This only impacts unaligned data compression (`-E48bit` with zstd, for example). [1] Commit 9e2f9d34dd12 ("erofs: handle overlapped pclusters out of crafted images properly") was originally introduced to handle crafted overlapped extents, but it addresses unaligned extents as well.
Quoted source text, attributed separately from HOL analysis.