From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99790: NFSD: stop registering with rpcbind after a failure in listener_set
Date: Fri, 20 Nov 2026 06:52:56 +0100 [thread overview]
Message-ID: <2026112035-CVE-2026-99790-df60@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
NFSD: stop registering with rpcbind after a failure in listener_set
nfsd_nl_listener_set_doit() calls svc_xprt_create_from_sa() once for each
requested listener and passes flags of 0, so every listener registers with
rpcbind on its own. A rpcbind that accepts the connection and never replies
therefore costs one timeout for each entry. With the cap of 1024 entries
the request can hold nfsd_mutex for about 34 minutes, which is roughly 17
times the hung-task threshold.
One failure is enough to know that the next call will not fare better.
Read svc_rpcb_failure_count() before the create loop, and pass
SVC_SOCK_ANONYMOUS for the rest of the request once the count moves.
The Linux kernel CVE team has assigned CVE-2026-99790 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit 16a471177496c8e04a9793812c187a2c1a2192fa and fixed in 6.12.118 with commit f21188d163fe7a6c930ef387af5937b9f7322725
Issue introduced in 6.10 with commit 16a471177496c8e04a9793812c187a2c1a2192fa and fixed in 6.18.64 with commit d7515faec4d1b3c67c1c18ec28abad83d90ef8c1
Issue introduced in 6.10 with commit 16a471177496c8e04a9793812c187a2c1a2192fa and fixed in 7.3.5 with commit 76ca00a4eca507550af13118289169bc4b508b82
Issue introduced in 6.10 with commit 16a471177496c8e04a9793812c187a2c1a2192fa and fixed in 7.4-rc1 with commit bf0f3a37e6ccb78ae80cc6eb2edde4f033c7574c
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99790
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/nfsd/nfsctl.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f21188d163fe7a6c930ef387af5937b9f7322725
https://git.kernel.org/stable/c/d7515faec4d1b3c67c1c18ec28abad83d90ef8c1
https://git.kernel.org/stable/c/76ca00a4eca507550af13118289169bc4b508b82
https://git.kernel.org/stable/c/bf0f3a37e6ccb78ae80cc6eb2edde4f033c7574c
reply other threads:[~2026-11-20 6:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026112035-CVE-2026-99790-df60@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.