CVE-2026-64262
Received Received - Intake

Use-After-Free in Linux Kernel fuse-uring

Vulnerability report for CVE-2026-64262, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-25

Last updated on: 2026-07-25

Assigner: kernel.org

Description

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).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-25
Last Modified
2026-07-25
Generated
2026-07-25
AI Q&A
2026-07-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Linux kernel vulnerability in the fuse-uring component. When io_uring cancels task work with specific conditions (like thread exit or ring context shutdown), the fuse_req reference is not properly released. This causes the fuse_req to remain linked indefinitely, blocking the originating syscall thread in a waiting state until the connection is aborted. It also prevents background request counters from decrementing, potentially stalling all future background operations once the limit is reached.

Detection Guidance

This vulnerability is specific to the Linux kernel's fuse-uring implementation and may not have direct network detection methods. Monitor for processes stuck in D-state (uninterruptible sleep) using commands like 'ps aux | grep D' or 'top'. Check for elevated fuse_req references or stalled io_uring operations in kernel logs with 'dmesg | grep -i fuse' or 'journalctl -k | grep -i fuse'.

Impact Analysis

This vulnerability can cause system hangs or performance degradation. Affected systems may experience unresponsive processes stuck in D-state (uninterruptible sleep) while waiting for a fuse request that never completes. Repeated exploitation could exhaust system resources by inflating background request counters, leading to stalled operations and potential denial-of-service conditions.

Mitigation Strategies

Apply the latest Linux kernel patches addressing this issue. If immediate patching is not possible, consider disabling io_uring for FUSE mounts or restricting access to fuse-related services. Monitor system logs for signs of exploitation or abnormal behavior in fuse operations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64262. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart