CVE-2026-68095

published 10 Aug 2026 · updated 17 Aug 2026

fuse-uring: fix race between registration and connection abortion

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2cd945492bc5b472e814272e88b731bb9bb17629, Kernel 3bca70235a706de76fe9a81defd37d987062c686 and Kernel 952b5d36f6a298f57c52a59e72076c69386a8aaf.

In the Linux kernel, the following vulnerability has been resolved: fuse-uring: fix race between registration and connection abortion This fixes this race: - thread a: io_uring_enter -> register sqe -> fuse_uring_create_ring_ent -> allocate ent but doesn't grab queue_ref yet - thread b: fuse_conn_destroy() -> fuse_chan_abort() -> fuse_uring_abort() is a no-op due to queue ref being 0 - thread a: grabs the queue_ref, queue_ref is now 1, rest of fuse_uring_do_register() logic executes - thread b: fuse_chan_abort() returns, fuse_chan_wait_aborted() now runs and calls "wait_event(ring->stop_waitq, atomic_read(&ring->queue_refs) == 0);" The abort/unmount thread will hang indefinitely in unkillable state as nothing will decrement queue_refs or wake stop_waitq, and the ring, queue, and ent are leaked. Fix this by checking fch->connected under fch->lock after the created ent has grabbed a ref count on the queue. This ensures that in the scenario above, it is guaranteed that we either release the queue ref and wake up stop_waitq (in case fuse_chan_wait_aborted() is already waiting) in fuse_uring_do_register() when we detect !fch->connected, or if the connection is aborted after the check, it is guaranteed that the async teardown worker will be running in the background cleaning up ents and decrementing the ent's ref on the queue, which will unblock the eventual queue and ring teardown.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.14, >=24fe962c86f55347385933a1b06ca71b60854690 <2cd945492bc5b472e814272e88b731bb9bb17629, >=24fe962c86f55347385933a1b06ca71b60854690 <3bca70235a706de76fe9a81defd37d987062c686, >=24fe962c86f55347385933a1b06ca71b60854690 <952b5d36f6a298f57c52a59e72076c69386a8aaf2cd945492bc5b472e814272e88b731bb9bb17629, 3bca70235a706de76fe9a81defd37d987062c686, 952b5d36f6a298f57c52a59e72076c69386a8aaf

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-68095 severity on Zeptric[![CVE-2026-68095](https://zeptric.io/badge/cve/CVE-2026-68095.svg)](https://zeptric.io/cve/CVE-2026-68095)