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 DD2EB2931DB for ; Mon, 27 Jul 2026 06:33:01 +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=1785133983; cv=none; b=T8RmZvpI2E/2phgV3RbmahFZmTFw69YYlR/eI4JH5iJQUegTc6un0xfbsu0agGQJJC8Lk0dQpum2jYe+j4OItLOCA3pF43v+rOcSnYS0HCPnH8HW9zGfW4BJosq4GcOXfoxW5j4kH3s/PvJWK/MTTGCbuacyO60wGWRXK9QZ2dU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785133983; c=relaxed/simple; bh=F0H+2PoLCHPtthQLjdDmhTODoEk569YG/r63eReonWs=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=QODx7yGGDzhhNCMrQamvdMqQAX7UGaduVn+vkJcjpYwXdLA/iFvtJYAdL0a6RDdeL4h491tX3W0n0GpBtd1Me7tz+6ehgL+/nWsBRdLd6VTXaAEWxVij6hJleABAB742FXiH8Erq96COs0klqY+UcD7WRoj6ovHDNV7UXsgFqIc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=NeEK/ezF; 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="NeEK/ezF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 31CB21F000E9; Mon, 27 Jul 2026 06:33:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1785133981; bh=sSWMta4ZVGkZ0g0aNe5RSAZdFXkzKtJ1DusfRpqz+kI=; h=From:To:Cc:Subject:Date:Reply-To; b=NeEK/ezF1n8usbtbD9KeiQYeZE7j2A3hvlZtlZt+6KjbXlfO30VzZPj8gJNOSZSnw 2/uBY/6cidtmeHU0/A+7tCdp9mC7wUmEYS/0+lF7veE7pblwuKmErDcBorU/edkfiQ G1HxJzyEHOEcFJOhCBU6Adg63QQ7LSotwmQbVpmU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64535: nvmet-tcp: Fix potential UAF when ddgst mismatch Date: Mon, 27 Jul 2026 08:32:34 +0200 Message-ID: <2026072735-CVE-2026-64535-e1f3@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=2934; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=LksW1Uku6ev2t1p0X2PibsyJYSvzww4XacPIaLRGSP8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlpv5sNVjZy6p/b/rMm3erK/Jq/r7K+z5z7fdPHx6cMe MKvXlQ60xHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATWVfMsODmUk7GbR+v7V1y +q/N43cchyPNu1czzM/kfi7Yd33/Dja5/LOXkx/Hy6s84QEA X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get. The Linux kernel CVE team has assigned CVE-2026-64535 to this issue. Affected and fixed versions =========================== Fixed in 6.1.178 with commit 96fe2513df590e74b04253a45089cae75569570e Fixed in 6.6.145 with commit e091ff83d962f9ed00d9bd70443676de9fe98bdc Fixed in 6.12.97 with commit 6f9442983a3e4227afd1c83a5251ddbca585ea21 Fixed in 6.18.40 with commit 088ee46c18d99baef453afd74181dd40ade044ad Fixed in 7.1 with commit dbbd07d0a7020b80f6a7028e561908f7b83b3d5a 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-64535 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: drivers/nvme/target/tcp.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/96fe2513df590e74b04253a45089cae75569570e https://git.kernel.org/stable/c/e091ff83d962f9ed00d9bd70443676de9fe98bdc https://git.kernel.org/stable/c/6f9442983a3e4227afd1c83a5251ddbca585ea21 https://git.kernel.org/stable/c/088ee46c18d99baef453afd74181dd40ade044ad https://git.kernel.org/stable/c/dbbd07d0a7020b80f6a7028e561908f7b83b3d5a