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=1795154016; b=Fv1NRM3wMHkZm04MjWLQvRfvd++2KFgzwjTt+DKsWD8yQbVxxLKC2PhuvA83xGw2OqZo RiLPBgX7aJLcgbvt7lzLgRyXKSsW/VU5ddx2Mb2PM+m2JJWe1R8oeYI8ZXxX1K26myB2T VKzw+aupCSeMQoD+5hl/BhyYtQmwKo1k+G3UkhJWfABNpNjUAT3gEet8YusX7086K05Ya RHi9/r6uErxKZe8qCme8Yz3USyZ6LHwzXhPgI671H5fUkVnyboqgDSALD9bY0w37JeyFK jlf0KD5XsqlOs1rVbybp2VFDndqYDzOp1b9Rs53RIjKScRwwvgjiEXZUK0+n/WiRGXw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154016; 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=IgGl/zX1v5LjybkXSXOUpjFNIiSYlx0Fr+LgOl0Gxk8=; b=P3r74JmeMXH9EOxfFS+gAGIoE+gfTeLIDDEou9xbVDim5uyASCHeNOROQrLvHSXy0wlq CTU5kQbQw2H5/0LdEAwO7DHAMupeGIzGrhM4vah5Wj7lueU010xT3D9que7lbU0Yfhofg gQSCZSfUR6/ppHEwRCEZuDz5eLaGvMQ99gXL8RsrjZ1LUigCuDh5JJKydRlf7HKI5+BJw nbjvOoI+L3ZEA8iE8f1ykVU64O18pVBrW2P2cqGQnELiefZh4Kp2zYIFOjAK3HRNLM5ie D1KJsQWJS+82wJyO2geZ73WZDrglbheMEFtFLrg01pXzQ+6H7MDpH4pPDS50K2STGJQ== 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=z+tNGVCO; 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 5FBEB606A326 for ; Fri, 20 Nov 2026 05:53:36 +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=z+tNGVCO Received: by smtp.kernel.org (Postfix) with ESMTPSA id A2B431F000C6; Fri, 20 Nov 2026 05:53:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154016; bh=IgGl/zX1v5LjybkXSXOUpjFNIiSYlx0Fr+LgOl0Gxk8=; h=From:To:Cc:Subject:Date:Reply-To; b=z+tNGVCOjNZQ4QZfGzQ0g0VoA3dCQrQOd6roiqjDCTNsa4IXajq0eAqgu8zYfBpes fQgOWy6v8bn/nGlGE/h/JhBspdpTzNtRG8CAEidtHogna8jT4dFKcpYUiykBW4j+FW 2S+lFKfW43pUHLmR9X/WCbVlyVB5YcMkACqhvP80= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99571: nvme-tcp: Validate the queue state under the queue lock in the address attribute Date: Fri, 20 Nov 2026 06:49:17 +0100 Message-ID: <2026112015-CVE-2026-99571-e86e@gregkh> X-Mailer: git-send-email 2.56.1 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=3529; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=l2djHcyqVWhJ4oP9Oa0XaciardsFy+AWUN5sSOBMrRA=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/78fsvnQohNtgW/8LJr2noUtYP/nHLlx3QNqW3Spql kfVoymNHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAnCTTRkW9Fye5yQrorCXbcZF 40Octtr67+68ZFiw+MrPgkePVGq9Ln73sop7VLlnbaYpAA== 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: nvme-tcp: Validate the queue state under the queue lock in the address attribute Reading the "address" sysfs attribute calls kernel_getsockname() on the admin queue socket, which can race with the queue teardown during connection error recovery: a reader can observe NVME_TCP_Q_LIVE set, then block on the queue lock while nvme_tcp_free_queue() releases the socket and clears queue->sock without holding the lock. Once the reader acquires the lock it dereferences the NULL socket pointer. Commit 76d54bf20cdc ("nvme-tcp: don't access released socket during error recovery") had the queue liveness check inside the lock. Commit 782373ba2766 ("nvme: tcp: avoid race between queue_lock lock and destroy") moved it back out because the lock itself is destroyed in nvme_tcp_free_queue(), so a reader arriving late trips mutex_destroy(). Check the queue liveness inside the queue lock, and clear queue->sock under the same lock. The teardown clears NVME_TCP_Q_LIVE under the lock well before the socket is released, so a reader either sees the bit cleared or a socket that cannot be released while it holds the lock. To also close the lock lifetime race, the queue locks are now owned by the controller: they are initialized with the queue array and only destroyed when the controller is freed, which cannot happen while a sysfs attribute read is still in progress. The queue count is computed by the NVME_TCP_OPT_NR_QUEUES() macro from the original connect options for both initialization and destruction, as reconnects may shrink ctrl->queue_count. The Linux kernel CVE team has assigned CVE-2026-99571 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit 782373ba27660ba7d330208cf5509ece6feb4545 and fixed in 7.3.5 with commit 0af6a8aede3121bc9662111665294731daddb13a Issue introduced in 6.12 with commit 782373ba27660ba7d330208cf5509ece6feb4545 and fixed in 7.4-rc1 with commit 2eeeaa9c1ff0c429096acc2947c296db6a56f96d Issue introduced in 6.1.118 with commit 4f946479b326a3cbb193f2b8368aed9269514c35 Issue introduced in 6.6.62 with commit 975cb1d2121511584695d0e47fdb90e6782da007 Issue introduced in 6.11.9 with commit e15cebc1b21856944b387f4abd03b66bd3d4f027 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-99571 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/host/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/0af6a8aede3121bc9662111665294731daddb13a https://git.kernel.org/stable/c/2eeeaa9c1ff0c429096acc2947c296db6a56f96d