# CVE-2026-68095: linux: In the Linux kernel, the following vulnerability has been resolved: fuse-uring: fix race between registration and co... CVE-2026-68095 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-68095, released August 11, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-68095 - Priority: High - CVSS: n/a (important) - EPSS: 0.0017 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Aug 10, 2026 ## 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. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel-livepatch-6.18.44-99.149 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | linux Debian 14 | 7.1.6-1 | [DEBIAN-CVE-2026-68095](https://patchblox.com/security/data/fix/linux/debian-cve-2026-68095.md) | Aug 11, 2026 | | Linux | microvm-kernel6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 | --- Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.