{"api_version":"1","generated_at":"2026-09-11T23:53:31+00:00","cve":"CVE-2026-80859","urls":{"html":"https://cve.report/CVE-2026-80859","api":"https://cve.report/api/cve/CVE-2026-80859.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80859","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80859"},"summary":{"title":"fuse: fix missing barrier when checking io-uring readiness","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->initialized and then fch->io_uring.\nfch->io_uring is set before fch->initialized, 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->initialized=1 but fch->io_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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-04 16:18:15","updated_at":"2026-09-11 10:16:52"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/dd9c835709f4bb3e4256eea7573e4e6e18f956de","name":"https://git.kernel.org/stable/c/dd9c835709f4bb3e4256eea7573e4e6e18f956de","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8974575898cd7a4c818088f102b2e7a0286d3302","name":"https://git.kernel.org/stable/c/8974575898cd7a4c818088f102b2e7a0286d3302","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/edb310bc27f0ad83e7fd558a3caf1a94ca511654","name":"https://git.kernel.org/stable/c/edb310bc27f0ad83e7fd558a3caf1a94ca511654","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80859","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80859","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3393ff964e0fa5def66570c54a4612bf9df06b76 8974575898cd7a4c818088f102b2e7a0286d3302 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3393ff964e0fa5def66570c54a4612bf9df06b76 dd9c835709f4bb3e4256eea7573e4e6e18f956de git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3393ff964e0fa5def66570c54a4612bf9df06b76 edb310bc27f0ad83e7fd558a3caf1a94ca511654 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.51 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.3 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80859","cve":"CVE-2026-80859","epss":"0.001450000","percentile":"0.040730000","score_date":"2026-09-07","updated_at":"2026-09-08 00:05:27"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/fuse/dev.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"8974575898cd7a4c818088f102b2e7a0286d3302","status":"affected","version":"3393ff964e0fa5def66570c54a4612bf9df06b76","versionType":"git"},{"lessThan":"dd9c835709f4bb3e4256eea7573e4e6e18f956de","status":"affected","version":"3393ff964e0fa5def66570c54a4612bf9df06b76","versionType":"git"},{"lessThan":"edb310bc27f0ad83e7fd558a3caf1a94ca511654","status":"affected","version":"3393ff964e0fa5def66570c54a4612bf9df06b76","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/fuse/dev.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.14"},{"lessThan":"6.14","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.51","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.3","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.51","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.3","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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->initialized and then fch->io_uring.\nfch->io_uring is set before fch->initialized, 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->initialized=1 but fch->io_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."}],"providerMetadata":{"dateUpdated":"2026-09-11T09:57:14.427Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/8974575898cd7a4c818088f102b2e7a0286d3302"},{"url":"https://git.kernel.org/stable/c/dd9c835709f4bb3e4256eea7573e4e6e18f956de"},{"url":"https://git.kernel.org/stable/c/edb310bc27f0ad83e7fd558a3caf1a94ca511654"}],"title":"fuse: fix missing barrier when checking io-uring readiness","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80859","datePublished":"2026-09-04T15:55:13.378Z","dateReserved":"2026-08-26T14:34:25.797Z","dateUpdated":"2026-09-11T09:57:14.427Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-04 16:18:15","lastModifiedDate":"2026-09-11 10:16:52","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80859","Ordinal":"1","Title":"fuse: fix missing barrier when checking io-uring readiness","CVE":"CVE-2026-80859","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80859","Ordinal":"1","NoteData":"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->initialized and then fch->io_uring.\nfch->io_uring is set before fch->initialized, 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->initialized=1 but fch->io_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.","Type":"Description","Title":"fuse: fix missing barrier when checking io-uring readiness"}]}}}