All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99367: NFSD: Don't complete a cld upcall the daemon has not read
Date: Thu, 19 Nov 2026 15:24:25 +0100	[thread overview]
Message-ID: <2026111951-CVE-2026-99367-7c8a@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

NFSD: Don't complete a cld upcall the daemon has not read

cld_pipe_downcall() matches a reply to its upcall on the xid alone.
A write that arrives before the daemon has read that upcall
completes __cld_pipe_upcall() while its struct rpc_pipe_msg is still
queued on the pipe. The waiter returns, its stack frame goes away,
and the pipe keeps a list_head that points into it. The next
rpc_queue_upcall() walks that pointer:

  BUG: KASAN: vmalloc-out-of-bounds in __list_add_valid_or_report
  Read of size 8 at addr ffffc90007027950 by task syz.0.96/13066
   __list_add_valid_or_report+0x6a/0x130
   rpc_queue_upcall
   cld_pipe_upcall
   nfsd4_cld_grace_start
   nfsd4_cld_tracking_init

The pipe is mode 0600 in rpc_pipefs, so the trigger is a broken or
hostile nfsdcld rather than an unprivileged task.

Record whether the daemon has consumed the whole message and
complete only when it has. cld_pipe_destroy_msg() runs on every path
by which the pipe releases a message, so it can maintain that flag
under cn_lock. nfsdcld sends its -EINPROGRESS downcalls only after
reading the upcall, so the new check does not break the GraceStart
record stream.

The Linux kernel CVE team has assigned CVE-2026-99367 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 3.4 with commit f3f8014862d813cca81a597c83bd1dbf0fb2b8f6 and fixed in 6.12.117 with commit e058341ceb177226fdb20a36d48fa827851d9c81
	Issue introduced in 3.4 with commit f3f8014862d813cca81a597c83bd1dbf0fb2b8f6 and fixed in 6.18.61 with commit f6d1f1072243a1adb1ae15425f6e36f86be94078
	Issue introduced in 3.4 with commit f3f8014862d813cca81a597c83bd1dbf0fb2b8f6 and fixed in 7.3.2 with commit 226c11eb20042ce4251f50870ce61f86581f8152
	Issue introduced in 3.4 with commit f3f8014862d813cca81a597c83bd1dbf0fb2b8f6 and fixed in 7.4-rc1 with commit 7f4bf851aca4e18940ebf2bddf4ba6783802ee81

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-99367
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/nfs4recover.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/e058341ceb177226fdb20a36d48fa827851d9c81
	https://git.kernel.org/stable/c/f6d1f1072243a1adb1ae15425f6e36f86be94078
	https://git.kernel.org/stable/c/226c11eb20042ce4251f50870ce61f86581f8152
	https://git.kernel.org/stable/c/7f4bf851aca4e18940ebf2bddf4ba6783802ee81

                 reply	other threads:[~2026-11-19 14:41 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=2026111951-CVE-2026-99367-7c8a@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.