Answer in brief
CVE-2026-64260 records a Unknown severity vulnerability in fuse-uring: Avoid queue->stopped races and set/read that value under lock. 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 | >=4a9bfb9b6850fec0685447aed280533cf980de70 <39c8e925b207afceffaa5382416ed405e0223a03 || >=4a9bfb9b6850fec0685447aed280533cf980de70 <4021a3a79eee551d95fe1e1e7c1b195d34ba8c08 || >=4a9bfb9b6850fec0685447aed280533cf980de70 <b70a3aca16934c196f92abb17b01c1647b9bb63c | 39c8e925b207afceffaa5382416ed405e0223a03, 4021a3a79eee551d95fe1e1e7c1b195d34ba8c08, b70a3aca16934c196f92abb17b01c1647b9bb63c |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Jul 25, 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: fuse-uring: Avoid queue->stopped races and set/read that value under lock There are several readers of queue->stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races 'struct fuse_req' might be freed with fuse_request_end, but another thread/cpu might already do teardown work.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64260 records a Unknown severity vulnerability in fuse-uring: Avoid queue->stopped races and set/read that value under lock. 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 | >=4a9bfb9b6850fec0685447aed280533cf980de70 <39c8e925b207afceffaa5382416ed405e0223a03 || >=4a9bfb9b6850fec0685447aed280533cf980de70 <4021a3a79eee551d95fe1e1e7c1b195d34ba8c08 || >=4a9bfb9b6850fec0685447aed280533cf980de70 <b70a3aca16934c196f92abb17b01c1647b9bb63c | 39c8e925b207afceffaa5382416ed405e0223a03, 4021a3a79eee551d95fe1e1e7c1b195d34ba8c08, b70a3aca16934c196f92abb17b01c1647b9bb63c |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Jul 25, 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: fuse-uring: Avoid queue->stopped races and set/read that value under lock There are several readers of queue->stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races 'struct fuse_req' might be freed with fuse_request_end, but another thread/cpu might already do teardown work.
Quoted source text, attributed separately from HOL analysis.