GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel FUSE: abort_on_kill returns without waiting for FR_FINISHED, freeing an in-flight request

UnscoredCVE-2026-80857Kernel, userspace & hypervisorcurated

Impact

On the abort_on_kill path, request_wait_answer() calls fuse_abort_conn() and returns without waiting for FR_FINISHED. If fuse_dev_do_write() is concurrently servicing the same request (FR_LOCKED set), the caller frees req->args while the device thread is still reading it - a kernel use-after-free. FUSE is ordinary infrastructure on GPU nodes: object-storage dataset and model mounts (s3fs, goofys, JuiceFS, gcsfuse) and virtiofs for VM and Kata sandboxes all run through it. The trigger is a task being killed at the wrong instant while a request is in flight, which a local user can attempt repeatedly. The record shows the use-after-free and the fix; it does not establish exploitability beyond that.

Who can reach it

Local user able to issue filesystem operations against a FUSE mount configured with abort_on_kill, and to have the issuing task killed. No elevated privileges needed; not reachable remotely.

What to do

Apply the stable kernel fix (linked commits, which jump to the existing wait_event(FR_FINISHED) instead of returning early) and reboot the node after draining it. No fixed release version is given in the record - only the commits.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.