Answer in brief
CVE-2026-64259 records a Unknown severity vulnerability in fuse-uring: make a fuse_req on SQE commit only findable after memcpy. 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 | >=c090c8abae4b6b77a1bee116aa6c385456ebef96 <e1711479e9068ea31b31353a702a51e639c3d059 || >=c090c8abae4b6b77a1bee116aa6c385456ebef96 <a635f427d57e2012102ae4886b48d8955c59fb86 || >=c090c8abae4b6b77a1bee116aa6c385456ebef96 <1efd3d474fc0ba74dfd984249bca78807d739812 | e1711479e9068ea31b31353a702a51e639c3d059, a635f427d57e2012102ae4886b48d8955c59fb86, 1efd3d474fc0ba74dfd984249bca78807d739812 |
| 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: make a fuse_req on SQE commit only findable after memcpy Bad userspace might try to trick us and send commit SQEs request unique / commit-id of requests that are not even send to fuse-server (io_uring_cmd_done() not called) yet. fuse_uring_commit_fetch() ends the fuse request when the ring entry has a wrong state, but that could have caused a use-after-free with the memcpy operations in fuse_uring_send_in_task(). In order to avoid such races the call of fuse_uring_add_to_pq() is moved after the copy operations and just before completing the io-uring request - malicious userspace cannot find the request anymore until all prepration work in fuse-client/kernel is completed. This also moves fuse_uring_add_to_pq() a bit up in the code to avoid a forward declaration. Also not with a preparation commit, to make it easier to back port to older kernels.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64259 records a Unknown severity vulnerability in fuse-uring: make a fuse_req on SQE commit only findable after memcpy. 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 | >=c090c8abae4b6b77a1bee116aa6c385456ebef96 <e1711479e9068ea31b31353a702a51e639c3d059 || >=c090c8abae4b6b77a1bee116aa6c385456ebef96 <a635f427d57e2012102ae4886b48d8955c59fb86 || >=c090c8abae4b6b77a1bee116aa6c385456ebef96 <1efd3d474fc0ba74dfd984249bca78807d739812 | e1711479e9068ea31b31353a702a51e639c3d059, a635f427d57e2012102ae4886b48d8955c59fb86, 1efd3d474fc0ba74dfd984249bca78807d739812 |
| 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: make a fuse_req on SQE commit only findable after memcpy Bad userspace might try to trick us and send commit SQEs request unique / commit-id of requests that are not even send to fuse-server (io_uring_cmd_done() not called) yet. fuse_uring_commit_fetch() ends the fuse request when the ring entry has a wrong state, but that could have caused a use-after-free with the memcpy operations in fuse_uring_send_in_task(). In order to avoid such races the call of fuse_uring_add_to_pq() is moved after the copy operations and just before completing the io-uring request - malicious userspace cannot find the request anymore until all prepration work in fuse-client/kernel is completed. This also moves fuse_uring_add_to_pq() a bit up in the code to avoid a forward declaration. Also not with a preparation commit, to make it easier to back port to older kernels.
Quoted source text, attributed separately from HOL analysis.