From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2FEB458F09C for ; Fri, 11 Sep 2026 20:05:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789157126; cv=none; b=Ug8I5a39kDwHKpu77YBPScjZUHyuHQKVSTEnAzh5Muit/d9N7MuwZYC2ojHbmhUFTrot2bB3w9Tk7Rw1A/HVdw5PbT4jHZluHSnlOkTeLlQVXZbWas0K8TbjmFxnLrcICPwWOKax/JGUmyx6//ebDdk/EFIBowQxDCuMQBSKSVY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789157126; c=relaxed/simple; bh=HJWIUKrNK3/mqCq6/gSYiwFCWqSh81lYGbmUEQBUJnA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=SoVboz+GbwPItBHBZStLDD7EBKPwhwHe+UmNUGZr/d1+Ziri1BmRr2/WqkHBGWHAklnUay9os951RYbNNIqr6r1IgQ/upf7T480k74p4M4a+nPuUPAAPA55484+mpUUH6CkNTl48sBzM2KW2fFd9xv8TuHvQoISaA+4tLiZ/dto= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=rI38Gvdm; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="rI38Gvdm" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DADE91F000FF; Fri, 11 Sep 2026 20:05:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789157120; bh=Y5qT1TzvE0r8hTuwzQ+gA7i+4GCyfJdGhKmzYD9/ILU=; h=From:To:Cc:Subject:Date:Reply-To; b=rI38GvdmpciCoAMQUMtDjBL1+C+Wtac1cdmgSvd4cdkqptPx5WjLPCPtww1UZdhtO zppq/mp/3hVuh37eMsRTm9AsTIcuBfiTdu4g9FhcyLsGXd0rqilvzXeq6nT0G81v5+ xZphLx7g0mbMO/W2aQxz4JzfQS9a784gtWzJmpEY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89699: nfsd: validate symlink target length in NFSv4 CREATE Date: Fri, 11 Sep 2026 21:46:28 +0200 Message-ID: <2026091155-CVE-2026-89699-6e8e@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2716; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=iCULa1RtuBwBPupLUxqddJYGoY8Xit6HxCRW2BlOw+E=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIptdixbofr2xLLnQ6cbP1Tzne871z77UsstDNLWKe 67vubNSHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCR5UcZFnSI1T6YE9txQHBR +OHoiEahHa4pZxjmyi48eDVti7TGzb3sD4uL1hxeXnTtPwA= 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: validate symlink target length in NFSv4 CREATE nfsd4_decode_create() accepts an unbounded cr_datalen from the wire for NF4LNK symlink targets, allowing a client to force a kmalloc of up to the maximum RPC payload size (several MiB) per COMPOUND op that persists until compound teardown. The VFS rejects oversized targets with ENAMETOOLONG, but the allocation has already occurred. Reject cr_datalen == 0 early with nfserr_inval and cr_datalen greater than NFS4_MAXPATHLEN (PATH_MAX) with nfserr_nametoolong to bound the allocation. The Linux kernel CVE team has assigned CVE-2026-89699 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.109 with commit b24843ea3de1676b29902457b38507c95a80649b Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18.50 with commit 895a485cd3758031ef9993c0d53cf19ce8fb4ccc Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.2.4 with commit 45ec115cbfecb4b3cfab7fca6f73d1b60696a25a Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.3-rc1 with commit 041f57056e5fb9c80adc088269322d2c61074406 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-89699 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/nfs4xdr.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/b24843ea3de1676b29902457b38507c95a80649b https://git.kernel.org/stable/c/895a485cd3758031ef9993c0d53cf19ce8fb4ccc https://git.kernel.org/stable/c/45ec115cbfecb4b3cfab7fca6f73d1b60696a25a https://git.kernel.org/stable/c/041f57056e5fb9c80adc088269322d2c61074406