GPU VulnDB

Database/Control plane, storage & DevOps

Linux nfsd: use-after-free when OFFLOAD_CANCEL or shutdown races the async COPY kthread

UnscoredCVE-2026-89675Control plane, storage & DevOpscurated

Impact

Several lifetime bugs in the async server-side COPY path let a teardown caller (OFFLOAD_CANCEL, nfsd4_shutdown_copy, nfsd4_cancel_copy_by_sb) race the copy kthread: the copy stays on clp->async_copies while refcounted, so release_copy_files() can run concurrently and double-put the nfsd_file; the STOPPED flag was set before the kthread's last dereferences of copy->nf_dst; copy_task was never pinned across kthread_stop(); and the embedded callback could outlive the copy. The result is use-after-free of nfsd_file and task_struct memory inside the kernel of the file server. A client that issues COPY and then OFFLOAD_CANCEL drives the race remotely, which on a storage node backing a GPU fleet means a kernel crash or worse for every job holding that mount.

Who can reach it

Any client that can mount the export and issue NFSv4.2 COPY plus OFFLOAD_CANCEL, subject to normal export authentication. Also reachable during export teardown on the server itself.

What to do

Upgrade to a stable kernel with the referenced commits and reboot the NFS server; the fix is in-kernel, so drain or fail over clients first. As an interim measure, exports served without NFSv4.2 async COPY (clients not using server-side copy) do not exercise this path. No fixed release numbers appear in the record.

References

Related entries

All Control plane, storage & DevOps 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.