GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel fuse: request left unlocked on return from fuse_ref_folio(), allowing a use-after-free

CVSS 7.8CVE-2026-64266Kernel, userspace & hypervisorcurated

Impact

fuse_ref_folio() unlocks the request and does not re-lock it before returning. fuse_chan_abort() can then end the request and the async end callback (for example fuse_writepage_free()) can free the args while the copy chain after fuse_ref_folio() is still reading them - a use-after-free in core FUSE. FUSE is ordinary infrastructure on GPU nodes: object-store and parallel-filesystem clients, container image mounts, and dataset loaders all use it, and unprivileged user namespaces let a tenant drive both sides of the channel. That makes the abort race reachable by a local workload rather than only by the storage admin.

Who can reach it

Local user able to mount or serve a FUSE filesystem, including a tenant with unprivileged user namespaces enabled in its container. The race is driven by aborting the FUSE channel while I/O is in flight.

What to do

Apply the stable fix that re-locks the request in fuse_ref_folio() and reboot the node. As an interim measure, disable unprivileged FUSE mounts for tenant workloads where the storage stack does not require them.

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.