CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's FUSE (Filesystem in Userspace) implementation, specifically in how it handles request states during processing and interruption. This flaw can lead to use-after-free conditions, potentially allowing an attacker to exploit stale entries in the interrupt list, resulting in data leakage to userspace. Organizations using Linux systems with FUSE should prioritize patching this vulnerability to mitigate the risk of unauthorized data exposure and system instability.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req When fuse_resend() moves a request from fpq->processing back to fiq->pending, it sets FR_PENDING and clears FR_SENT but does not remove the requests intr_entry from fiq->interrupts. If the request had FR_INTERRUPTED set from a prior signal, intr_entry remains dangling on fiq->interrupts. When the requesting task then receives a fatal signal, fuse_remove_pending_req() sees FR_PENDING=1, removes the request from fiq->pending and frees it via the refcount path, also without cleaning intr_entry. The stale intr_entry causes use-after-free when fuse_read_interrupt() iterates fiq->interrupts: - list_del_init(&req->intr_entry) -> UAF write on freed slab - req->in.h.unique -> UAF read, data leaked to userspace Remove intr_entry from fiq->interrupts in fuse_resend() for interrupted requests before they are placed back on fiq->pending. Add a WARN_ON if the intr_entry is not empty on request destruction.
Related CVEs
Other vulnerabilities affecting the same vendor(s)