CVE-2026-99372: NFSD: cap the number of listeners accepted in listener_set
In the Linux kernel, the following vulnerability has been resolved:
NFSD: cap the number of listeners accepted in listenerset
nfsdnllistenersetdoit() matches each requested listener against the existing set. The nested loop that does this is O(N M), where N is the requested count and M is the existing count. The loop runs under svlock with bottom halves disabled. A userland request with a very large listener list can therefore spin in atomic context for a long time.
Reject a request that carries more than NFSDNLLISTENERMAX (1024) entries. The check goes in nfsdnlvalidatelisteners(), before the code takes any lock. The limit is far above any realistic configuration.
This patch does not cap M. Only the message size bounded N; real sockets bound M. A listenerset result set is the requested set, so that path also holds M at the cap, but writeportsaddxprt() adds two listeners per call and removes none, so repeated calls can push M past it. The worst case under svlock is therefore 1024 M, plus 1024 nlaparsenested() calls. Both interfaces require CAPNETADMIN.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Compensating control
In NFSD listener_set handling, reject requests with more than NFSD_NL_LISTENER_MAX (1024) listeners and bound the existing listener count to the same limit.