CVE-2026-68095
Last modified
CVE-2026-68095 is a vulnerability of currently unknown severity. 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..
Description
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 24fe962c86f55347385933a1b06ca71b60854690, < 3bca70235a706de76fe9a81defd37d987062c686; >= 24fe962c86f55347385933a1b06ca71b60854690, < 2cd945492bc5b472e814272e88b731bb9bb17629; >= 24fe962c86f55347385933a1b06ca71b60854690, < 952b5d36f6a298f57c52a59e72076c69386a8aaf |
| Linux | Linux | 6.14 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68095?
How severe is CVE-2026-68095?
How do I fix CVE-2026-68095?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-6809The Social Post Embed plugin for WordPress is vulnerable to …6.4
- CVE-2026-68090In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68091In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68092In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68093In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68094In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68096In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68097In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68098In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68099In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6810The Booking Calendar Contact Form plugin for WordPress is vu…5.3
- CVE-2026-68100In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68095?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
