Answer in brief
CVE-2026-64588 records a High severity (CVSS 7.8) vulnerability in fuse-uring: fix data races on ring->ready. 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.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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c2c9af9a0b13261c36909036057a116f2edb5e1a <b156bb9966972122b148acab8bdf415cdb8176a3 || >=c2c9af9a0b13261c36909036057a116f2edb5e1a <d01a09b442cb786cd44ccc7c84d57e2856d6737c || >=c2c9af9a0b13261c36909036057a116f2edb5e1a <46725a0056c884cf58a6897f222892807327d82d | b156bb9966972122b148acab8bdf415cdb8176a3, d01a09b442cb786cd44ccc7c84d57e2856d6737c, 46725a0056c884cf58a6897f222892807327d82d |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
In the Linux kernel, the following vulnerability has been resolved: fuse-uring: fix data races on ring->ready On weakly-ordered architectures, the store to fiq->ops can be reordered past the store to ring->ready, allowing a CPU that sees ring->ready == true via fuse_uring_ready() to dispatch requests through a stale fiq->ops pointer. Upgrade the store to smp_store_release() and the load in fuse_uring_ready() to smp_load_acquire() so that the preceding WRITE_ONCE(fiq->ops, ...) is visible to any CPU that observes ring->ready == true. Additionally, fuse_uring_do_register() publishes ring->ready with WRITE_ONCE() but the fast-path check reads it with a plain load. This is a marked-vs-unmarked access that KCSAN will flag. Wrap it in READ_ONCE() to mark it without adding unnecessary ordering. Also wrap the fc->ring load in fuse_uring_ready() in READ_ONCE() to prevent the compiler from reloading it between the NULL check and the dereference.
Quoted source text, attributed separately from HOL analysis.