Answer in brief
CVE-2026-80859 records a Unknown severity vulnerability in fuse: fix missing barrier when checking io-uring readiness. 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.
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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3393ff964e0fa5def66570c54a4612bf9df06b76 <dd9c835709f4bb3e4256eea7573e4e6e18f956de || >=3393ff964e0fa5def66570c54a4612bf9df06b76 <edb310bc27f0ad83e7fd558a3caf1a94ca511654 | dd9c835709f4bb3e4256eea7573e4e6e18f956de, edb310bc27f0ad83e7fd558a3caf1a94ca511654 |
| Linux/Linuxgeneric | 6.14 | Not reported |
| Linux/Linuxgeneric | >=3393ff964e0fa5def66570c54a4612bf9df06b76 <8974575898cd7a4c818088f102b2e7a0286d3302 || >=3393ff964e0fa5def66570c54a4612bf9df06b76 <dd9c835709f4bb3e4256eea7573e4e6e18f956de || >=3393ff964e0fa5def66570c54a4612bf9df06b76 <edb310bc27f0ad83e7fd558a3caf1a94ca511654 | 8974575898cd7a4c818088f102b2e7a0286d3302, dd9c835709f4bb3e4256eea7573e4e6e18f956de, edb310bc27f0ad83e7fd558a3caf1a94ca511654 |
Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 4, 2026
In the Linux kernel, the following vulnerability has been resolved: fuse: fix missing barrier when checking io-uring readiness fuse_block_alloc() reads fch->initialized and then fch->io_uring. fch->io_uring is set before fch->initialized, ordered by the smp_wmb() in fuse_chan_set_intialized(), but fuse_block_alloc() has no matching read barrier between the two loads. This may lead a CPU to observe fch->initialized=1 but fch->io_uring=0, and skip the check that blocks request allocation until the io-uring queues are ready. This can reintroduce the lock-order inversion deadlock that commit 3393ff964e0f prevents. Add an smp_rmb() barrier to pair with the smp_wmb() in fuse_chan_set_initialized() to prevent this.
Quoted source text, attributed separately from HOL analysis.