linux: In the Linux kernel, the following vulnerability has been resolved: fuse-uring: end fuse_req on io-uring cancel task...
CVE-2026-64262 is fixed in 20 products on 1 platform, first by ALAS2023-2026-2045, released August 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: fuse-uring: end fuse_req on io-uring cancel task work When io_uring delivers task work with tw.cancel set (PF_EXITING, PF_KTHREAD fallback, or percpu_ref_is_dying on the ring context), fuse_uring_send_in_task() takes the cancel branch, assigns -ECANCELED, and falls through to fuse_uring_send(). That path only flips the entry to FRRS_USERSPACE and completes the io_uring cmd; it never discharges the ring entry's owning reference to the fuse_req that fuse_uring_add_req_to_ring_ent() handed it at dispatch time. fuse_uring_send_in_task() tw.cancel == true err = -ECANCELED fuse_uring_send(ent, cmd, err, issue_flags) ent->state = FRRS_USERSPACE list_move(&ent->list, &queue->ent_in_userspace) ent->cmd = NULL io_uring_cmd_done(-ECANCELED) /* ent->fuse_req still set, req still hashed */ The fuse_req stays linked on fpq->processing[hash] and fuse_request_end() is never invoked. The originating syscall thread blocks in D-state in request_wait_answer() until fuse_abort_conn() runs, which can be the entire connection lifetime. For FR_BACKGROUND requests fc->num_background is never decremented either, so repeated cancels inflate the counter until max_background is hit and all later background ops stall. tw.cancel does not imply a connection abort (e.g. a single io_uring worker thread exits while the fuse connection stays up), so this cannot be left for fuse_abort_conn() to clean up. Ending the req but still routing the entry through fuse_uring_send() is not enough: that leaves a req-less entry on ent_in_userspace, and ent_list_request_expired() dereferences ent->fuse_req unconditionally on the head of that list, which would then NULL-deref. Fix the cancel branch to release the entry directly. Remove it from the queue, complete the io_uring cmd, end the fuse_req, free the entry, and drop its queue_refs (waking the teardown waiter if it was the last).
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| bpftool6.18-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel-livepatch-6.18.39-79.141 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-debuginfo-common-aarch64 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-debuginfo-common-x86_64 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-devel · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-headers · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-modules-extra · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-modules-extra-common · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-tools · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-tools-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| kernel6.18-tools-devel · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| linux · Debian 14 | 7.1.4-1 | DEBIAN-CVE-2026-64262 | Aug 7, 2026 |
| microvm-kernel6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| perf6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| perf6.18-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| python3-perf6.18 · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
| python3-perf6.18-debuginfo · amzn 2023 | 1:6.18.39-79.141.amzn2023 | ALAS2023-2026-2045 | Aug 3, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
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.