GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel nfsd: transports routed to threadless service pools hang the connection indefinitely

CVSS 7.5CVE-2026-89549Kernel, userspace & hypervisorcurated

Impact

When nfsd runs in pernode or percpu pool mode with fewer threads than the host has NUMA nodes, svc_set_num_threads leaves trailing pools with zero threads. A connection that lands on such a pool is queued on sp_xprts and never serviced, so the client hangs forever rather than erroring. GPU nodes are routinely multi-socket, high-NUMA machines, which is exactly the configuration that produces empty pools; the symptom looks like a network fault and jobs block on dataset or checkpoint I/O until the mount is torn down.

Who can reach it

No authentication or attacker required in the usual case - it is a misconfiguration-triggered hang reachable by any NFS client whose connection is accepted on a CPU belonging to a threadless pool. NVD scores it as network-reachable availability loss.

What to do

Update the host kernel to a stable release carrying the svc_pool_for_cpu() fix and reboot the NFS server. Until then, the practical mitigation is to raise the nfsd thread count to at least the number of service pools (NUMA nodes or CPUs, depending on pool mode) or switch the pool mode to global - both are runtime changes on the server, no reboot needed.

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.