{"api_version":"1","generated_at":"2026-09-11T23:53:31+00:00","cve":"CVE-2026-80858","urls":{"html":"https://cve.report/CVE-2026-80858","api":"https://cve.report/api/cve/CVE-2026-80858.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80858","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80858"},"summary":{"title":"fuse: publish io-uring queues with release semantics","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfuse: publish io-uring queues with release semantics\n\nfuse_uring_create_queue() initializes a fuse_ring_queue and then\npublishes the pointer into ring->queues[qid] with WRITE_ONCE() under the\nfch->lock. There are several readers that may concurrently be fetching\nthat pointer locklessly and then deferencing it.\n\nWRITE_ONCE() doesn't ensure ordering of the queue's field\ninitialization before the ring->queues[qid] pointer assignment. The\nqueue must be published with smp_store_release() so the field\ninitialization is guaranteed to happen before.\n\nReaders in paths where the read may happen concurrently with the store\nneed to use READ_ONCE() because any race involving a plain access is\nundefined.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-04 16:18:14","updated_at":"2026-09-11 10:16:51"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a5bb215dbc34b4c6a5e144ea1416bf66450d519f","name":"https://git.kernel.org/stable/c/a5bb215dbc34b4c6a5e144ea1416bf66450d519f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/42df916e5a5f8fb4b60c8cefb54318d1ec02c580","name":"https://git.kernel.org/stable/c/42df916e5a5f8fb4b60c8cefb54318d1ec02c580","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aa","name":"https://git.kernel.org/stable/c/a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aa","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80858","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80858","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 24fe962c86f55347385933a1b06ca71b60854690 a5bb215dbc34b4c6a5e144ea1416bf66450d519f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 24fe962c86f55347385933a1b06ca71b60854690 a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aa git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 24fe962c86f55347385933a1b06ca71b60854690 42df916e5a5f8fb4b60c8cefb54318d1ec02c580 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":"80858","cve":"CVE-2026-80858","epss":"0.001450000","percentile":"0.040720000","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_uring.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a5bb215dbc34b4c6a5e144ea1416bf66450d519f","status":"affected","version":"24fe962c86f55347385933a1b06ca71b60854690","versionType":"git"},{"lessThan":"a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aa","status":"affected","version":"24fe962c86f55347385933a1b06ca71b60854690","versionType":"git"},{"lessThan":"42df916e5a5f8fb4b60c8cefb54318d1ec02c580","status":"affected","version":"24fe962c86f55347385933a1b06ca71b60854690","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/fuse/dev_uring.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: publish io-uring queues with release semantics\n\nfuse_uring_create_queue() initializes a fuse_ring_queue and then\npublishes the pointer into ring->queues[qid] with WRITE_ONCE() under the\nfch->lock. There are several readers that may concurrently be fetching\nthat pointer locklessly and then deferencing it.\n\nWRITE_ONCE() doesn't ensure ordering of the queue's field\ninitialization before the ring->queues[qid] pointer assignment. The\nqueue must be published with smp_store_release() so the field\ninitialization is guaranteed to happen before.\n\nReaders in paths where the read may happen concurrently with the store\nneed to use READ_ONCE() because any race involving a plain access is\nundefined."}],"providerMetadata":{"dateUpdated":"2026-09-11T09:57:11.882Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a5bb215dbc34b4c6a5e144ea1416bf66450d519f"},{"url":"https://git.kernel.org/stable/c/a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aa"},{"url":"https://git.kernel.org/stable/c/42df916e5a5f8fb4b60c8cefb54318d1ec02c580"}],"title":"fuse: publish io-uring queues with release semantics","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80858","datePublished":"2026-09-04T15:55:12.442Z","dateReserved":"2026-08-26T14:34:25.797Z","dateUpdated":"2026-09-11T09:57:11.882Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-04 16:18:14","lastModifiedDate":"2026-09-11 10:16:51","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80858","Ordinal":"1","Title":"fuse: publish io-uring queues with release semantics","CVE":"CVE-2026-80858","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80858","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nfuse: publish io-uring queues with release semantics\n\nfuse_uring_create_queue() initializes a fuse_ring_queue and then\npublishes the pointer into ring->queues[qid] with WRITE_ONCE() under the\nfch->lock. There are several readers that may concurrently be fetching\nthat pointer locklessly and then deferencing it.\n\nWRITE_ONCE() doesn't ensure ordering of the queue's field\ninitialization before the ring->queues[qid] pointer assignment. The\nqueue must be published with smp_store_release() so the field\ninitialization is guaranteed to happen before.\n\nReaders in paths where the read may happen concurrently with the store\nneed to use READ_ONCE() because any race involving a plain access is\nundefined.","Type":"Description","Title":"fuse: publish io-uring queues with release semantics"}]}}}