GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel nfsd: missing cl_lock in client_has_openowners() allows use-after-free during EXCHANGE_ID

UnscoredCVE-2026-99310Kernel, userspace & hypervisorcurated

Impact

client_has_openowners() walks a client's openowner list without holding cl_lock while another path frees openowners under that lock. A concurrent NFSv4.1+ EXCHANGE_ID with mismatched credentials can therefore use freed kernel memory in nfsd. The record shows a KASAN use-after-free and does not establish anything beyond memory corruption in the server kernel, but on an NFS server that GPU nodes depend on for datasets or home directories, a crash takes out storage for every client. It requires winning a race.

Who can reach it

An NFSv4.1+ client that can reach the nfsd server and send EXCHANGE_ID requests, racing against state teardown for an existing client. Network-reachable. The record does not say whether authentication is needed beyond what the export permits. Only hosts running the in-kernel NFS server are affected.

What to do

Install a kernel with the stable fix on NFS servers and reboot them, which interrupts every client unless the server is part of an HA pair. Restricting nfsd to trusted client networks reduces exposure until then.

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.