CVE-2026-80859
fuse: fix missing barrier when checking io-uring readiness
Reported by linux · Published September 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.
EPSS 0.16% · 4.7th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.18-headers | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.18-tools-devel | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| python3-perf6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| microvm-kernel6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.18-modules-extra-common | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| perf6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.18-devel | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| Linux | Linux | edb310bc27f0ad83e7fd558a3caf1a94ca511654, dd9c835709f4bb3e4256eea7573e4e6e18f956de |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 3393ff964e0fa5def66570c54a4612bf9df06b76, 3393ff964e0fa5def66570c54a4612bf9df06b76, 3393ff964e0fa5def66570c54a4612bf9df06b76 |
| Linux | Linux | 6.14, 0, 6.18.51 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| Linux | Linux | 3393ff964e0fa5def66570c54a4612bf9df06b76, 7.3, 6.18.51 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel-livepatch-6.18.51-120.162 | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| linux | linux_kernel | 6.14, 6.14, 6.14 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (11 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80859
vulnetix vdb fixes CVE-2026-80859
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80859/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart