From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795099299; b=V/huhb2jICihS7c/NmhHomf7FUj+VkfYOW3eDkcMATgzR0FZuUM/GLbR1jGFqUZZ5iX8 w1xHdLV+8y1dA8zPuEnxtBnMYvinivB3ncmx8A3CfTarXSVom2Fry9Pmt0ZLP4QCAsqHb SGLbM/LQl13S5/a+ego9pkJAkhUp+aXpq5aaEaX2q5M+4Pqww7TRtNvPDH5wUwthdZXgw wZzcCN9kB5ifQqsALyiOJxKJdFxnTL+qC6iQOJ13Cmy1JJGEqPcKrxKctM7zKsa5peWef 58H5A51AhIeedEGVQA/unYyBUysrmldN2jk52StoPiKjDN6m2GxfTkHaBgezjOhGgVQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795099299; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=+KgbRMPf/dLibv0gcB0WtgMOC7efg1W1F95OHXe/sVU=; b=TC5J7t/YkQfr4zQbdc1zCvWQhqU7KUTADHuRT8Lrz1oM30q9wpyvmtJ5cB0+vU2TBWTD anuvT+ArlrQsgbYXByQvEEzLksc2rnr+EWBD/t+Cz+xpYH/cJIxwqM+cOrdrOqkJB5jiK WieogDCtDXCCp3G5Bd9beltEuAmz0dUA8UdJLRPKGMymV0vssXXSSYiQ+1Y8SCrAN5Ria i6WFF/N3J9XDvfSZvaV+PiNWhs5YeffQ8pMtaUQHWPwh5bhRIWMTc+Msg6NqU/vCRSF6d aKvUozcmnvnFRRIHjJq1BQZcz+whgS+cJoldbs0OiZbc6cRNZtlaWewjfwKacWnuN0Q== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=zxT5He3Y; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 73143606A320 for ; Thu, 19 Nov 2026 14:41:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=zxT5He3Y Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8FAB71F000C5; Thu, 19 Nov 2026 14:41:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795099299; bh=+KgbRMPf/dLibv0gcB0WtgMOC7efg1W1F95OHXe/sVU=; h=From:To:Cc:Subject:Date:Reply-To; b=zxT5He3YWVj6fizxdpbTWEi7jFOw5Q6j9p/FRFysvwEO9Dk+H6RN54EA12aTCAS2o O39HJV+ex/xpdPuqdN+wKRBLh9lAYGUK73UNRy89DbJZo8mql+L10Buh3yep2Ebhbq 8orhLlD40iM5uhE4zI49gf/iH3bdwPf3H/5xp314= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman 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 Message-ID: <2026111951-CVE-2026-99367-7c8a@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3334; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=UbCI3mmsDmhFIByiaVrNF06oSX507oElRl0yEwjuuf8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2cobRA+sKZPJmXTtZ2zCGmb5SKPZioc7a6+5825NP 9N5/VRuRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEykcgfDgsvWnJ3ld67U9LRU nHzxcUY0i5DiK4YFJ3n5Dx+WqBHlkL5fPrfk1QkDj/PlAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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