{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80859 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80859 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80859 and fix it if it is affected.\n\nWhat it is: CVE-2026-80859 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80859 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80859/ (Markdown: https://insights.sbomify.com/CVE-2026-80859/index.md)","id":"CVE-2026-80859","markdown":"https://insights.sbomify.com/CVE-2026-80859/index.md","name":"CVE-2026-80859","record":{"aliases":["BELL-CVE-2026-80859","DEBIAN-CVE-2026-80859","GHSA-66f3-f7p7-8q9g","UBUNTU-CVE-2026-80859"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A missing memory barrier in the Linux kernel FUSE module can cause a race condition leading to a deadlock and denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix missing barrier when checking io-uring readiness\n\nfuse_block_alloc() reads fch-\u003einitialized and then fch-\u003eio_uring.\nfch-\u003eio_uring is set before fch-\u003einitialized, ordered by the smp_wmb()\nin fuse_chan_set_intialized(), but fuse_block_alloc() has no matching\nread barrier between the two loads.\n\nThis may lead a CPU to observe fch-\u003einitialized=1 but fch-\u003eio_uring=0,\nand skip the check that blocks request allocation until the io-uring\nqueues are ready. This can reintroduce the lock-order inversion deadlock\nthat commit 3393ff964e0f prevents.\n\nAdd an smp_rmb() barrier to pair with the smp_wmb() in\nfuse_chan_set_initialized() to prevent this.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"fuse: fix missing barrier when checking io-uring readiness","id":"CVE-2026-80859","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"fuse: fix race between interrupt and resend","id":"CVE-2026-80860"},"packages":[],"prev":{"headline":"fuse: publish io-uring queues with release semantics","id":"CVE-2026-80858"},"products":["Linux"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A missing memory barrier in the Linux kernel FUSE module can cause a race condition leading to a deadlock and denial of service.","url":"https://insights.sbomify.com/CVE-2026-80859/"}