From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 6D4163A5434 for ; Fri, 8 May 2026 14:22:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250146; cv=none; b=jIMj3o48iveehsLRWbRiu0fzX114hBgcozyv7KhNVVUSJXHk46eaptDsNAbYzg5yHwO0r60oT75kx3wBoD28ejZ1hfElCx2ZHr8yC4CuZ4ycEumbppEUmUlRgqpfPgLjS0iIkOxTWITS+UBnaAcK0ot3DeqAcWYsMjHSNGcOkAU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250146; c=relaxed/simple; bh=1BBma6UynBa7nSqO34Gy95c00D74xANsroYzoUrh5fc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=usWH/kevYabKTDSIJUWOqmhXl+M7nKXYuM3N2UIIub/uD+vmL5BX5V3U3rdLCG18mGr9gZLGyeRvmuWhIMSObbxca1jMuiiqXrYyyeygjtRHqNo+ZzOZZbMxPSzbIxHb8p7bcFp5mu0MY0BER6yoXOXBYFJTYlb0khTg/ZRBTK4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=v0oqSS+N; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="v0oqSS+N" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E8604C2BCB0; Fri, 8 May 2026 14:22:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778250146; bh=1BBma6UynBa7nSqO34Gy95c00D74xANsroYzoUrh5fc=; h=From:To:Cc:Subject:Date:Reply-To:From; b=v0oqSS+NOwdLxaHZexr8oHKiuOZ4819EjvQnWDdeyJq/YeHyIkihO5KHt73o2WJs8 Qj0bBot5J2oZlcuISSk+8Do7iNHJz8uVK9Vgo0f7t4aCzrXMMBJtWuc+qnBWaJQ61Y Si/rTa6KDK5l54w7mrrbOkmKWs4Db6FJAJ6aZL7E= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43362: smb: client: fix in-place encryption corruption in SMB2_write() Date: Fri, 8 May 2026 16:21:31 +0200 Message-ID: <2026050826-CVE-2026-43362-d301@gregkh> X-Mailer: git-send-email 2.54.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=2936; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=00u+9hy3cUQN0ragzkVo5ebsCfkGx7E0g0Uh9wg+Ork=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/P6ZtKH0QLu7119nhwH6/WqkNF7RFRO2vdXht4TD0S 3I5nWXSEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABM59I1hQe/vFwaSrD7HhB0u vdgnWaJzrnevN8OClvORd61v8/UtqXI03awlc1t2hmk7AA== 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: smb: client: fix in-place encryption corruption in SMB2_write() SMB2_write() places write payload in iov[1..n] as part of rq_iov. smb3_init_transform_rq() pointer-shares rq_iov, so crypt_message() encrypts iov[1] in-place, replacing the original plaintext with ciphertext. On a replayable error, the retry sends the same iov[1] which now contains ciphertext instead of the original data, resulting in corruption. The corruption is most likely to be observed when connections are unstable, as reconnects trigger write retries that re-send the already-encrypted data. This affects SFU mknod, MF symlinks, etc. On kernels before 6.10 (prior to the netfs conversion), sync writes also used this path and were similarly affected. The async write path wasn't unaffected as it uses rq_iter which gets deep-copied. Fix by moving the write payload into rq_iter via iov_iter_kvec(), so smb3_init_transform_rq() deep-copies it before encryption. The Linux kernel CVE team has assigned CVE-2026-43362 to this issue. Affected and fixed versions =========================== Fixed in 6.6.130 with commit 438e77435aee2894d5edf90be5c87004a57f6258 Fixed in 6.12.78 with commit 52327268224fb9ccc7ecfbbdfdfff54b6e93c518 Fixed in 6.18.19 with commit 92e64f1852f455f57d0850989e57c30d7fac7d95 Fixed in 6.19.9 with commit aea5e37388a080361110ab5790f57ae0af383650 Fixed in 7.0 with commit d78840a6a38d312dc1a51a65317bb67e46f0b929 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-43362 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/smb/client/smb2pdu.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/438e77435aee2894d5edf90be5c87004a57f6258 https://git.kernel.org/stable/c/52327268224fb9ccc7ecfbbdfdfff54b6e93c518 https://git.kernel.org/stable/c/92e64f1852f455f57d0850989e57c30d7fac7d95 https://git.kernel.org/stable/c/aea5e37388a080361110ab5790f57ae0af383650 https://git.kernel.org/stable/c/d78840a6a38d312dc1a51a65317bb67e46f0b929