cve.bz

CVE-2026-80859 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-80859 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80859?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80859?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80859 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.14 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.51
Linux7.27.2.3
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.2.6-1DEBIAN-CVE-2026-80859
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-80859
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-80859
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-80859
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-80859
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-80859 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-80859 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-80859 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-80859 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-80859 USN-9020-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 moreno fix listedUBUNTU-CVE-2026-80859
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-80859
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-80859 USN-8959-1
12 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.5-1.1openSUSE-SU-2026:11773-1
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-80859

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because triggering the flaw requires local execution rights to interact with FUSE, and the resulting deadlock leads to a denial of service without exposing sensitive data or permitting privilege escalation. Exploitation depends on race conditions between thread allocations and queue setup in the io-uring interface for user-space filesystems. Supported Red Hat Enterprise Linux releases do not include the underlying FUSE io-uring functionality in their kernels and are not affected by this issue.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80859.

References

Check your stackJSON