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=1795154526; b=hSisCHwQq1aNVkceHnRMTx+I0YesWl7KiEOc5Ug31KherAhvjG94SWOGGG+/5JHyLStC YBA1Y7QM/VzLfhwAYldVj4tNBtaFx6ovxAoDoSmg9Zb2N1XZ8cm02hKUlfrnRmFNLa+rd jlfKX/1VyuZuUy2e9E11sO77/xymjuYYPlAsH4eGL1cQZ7UuCApdIpKBPEgjGUZQC+VVw omDbAA/g70nYTeUif+ho3EkB+W3j8FoOiiuOEJ21VqdWFoxEZvMVYKUm/zcgl6BEr+E52 ybe/W9qHciwWDbyj83GK47RLVav1Y69uXRFfLtqIIvZQjGxScFu184uGrnLPvtA3w0g== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154526; 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=e9ba9RMv+RcBn4tTxnUT0Sku83dwe7ZRPArMTvcdypc=; b=xDLc+bg9rTi/B0p+ADKrH/2eBjIuAzfZHoRJznwCtOGBFHWhT8ttUhZTNyTKeqmgFyqW cQ8pIzblI3J0XvHJSxOKNZbZexB1o0fzFpYMcDvUToBG3xBGrxmCNzqAcIQ+Djy0h5j33 9yGGE6uKJ+FSd1NsK6BzxRPedHExeUT4RnZ2fkye5T3i+hgz5UoWpDnChzHB1OO6NP7Pj 5UO1khur5hlC1RNxeCGpBZSbPCesg/e5rdu0AbfLCXIFs6iOv+a3jhuK8zF2NxcDKG3j4 RT+S7ZJTypAnV/PznrElTGgpr/sVGLMQjaXQqKoHZw2dhhCeFG5x80udFxQxXCxxcTQ== 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=GWbbSiYE; 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 72484606A521 for ; Fri, 20 Nov 2026 06:02:06 +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=GWbbSiYE Received: by smtp.kernel.org (Postfix) with ESMTPSA id 707661F000CA; Fri, 20 Nov 2026 06:02:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154526; bh=e9ba9RMv+RcBn4tTxnUT0Sku83dwe7ZRPArMTvcdypc=; h=From:To:Cc:Subject:Date:Reply-To; b=GWbbSiYEWverG8dDLDDHR7Y2PWsnNRRc38HUMMbG027OU0HPj3I0Slks1G6GgZf5D ScLytyjTFfq0CUNUqgIeK34DkPjdxoi9zMFBsP96BjJ2DQckHCrDcEWFsHpHs84pon 4AKrikIE98Yj+3Z/9xnNqYSCVejgnmUBok6rSpCQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99774: xfrm: espintcp: reorder operations within espintcp_init_sk Date: Fri, 20 Nov 2026 06:52:40 +0100 Message-ID: <2026112029-CVE-2026-99774-b686@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=2669; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=w6/vZmg+aiNjb2hQXRHJK9Dvd5yqRvsE93aC2hCes4w=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7y8V+G0fK16sEC15m/eIb/3264cCH/PuaZR56+P3a b6Or+GkjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhI8kOGuTIrdfje/zmrl2h2 tC3bdP2fJZeN3wFFDRNvrxO7+6eLZ+3ebbblz56pGVkDAA== 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: xfrm: espintcp: reorder operations within espintcp_init_sk When enabled on a socket, espintcp sets the socket callbacks to its own before it has finished setting up its context and published it as icsk_ulp_data. Any one of those callbacks that gets called before will dereference a NULL icsk_ulp_data. Fix this by reording the operations, and add memory barriers to ensure callers will have a struct espintcp_ctx available. Add a few WRITE_ONCE/READ_ONCE too while we're there. The Linux kernel CVE team has assigned CVE-2026-99774 to this issue. Affected and fixed versions =========================== Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.12.118 with commit 6653f281a84dfc050042b837fbf0a1ab87f8f645 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.18.64 with commit d50065a04b8b2edd9215a1960a48c4a4667a5b8c Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 7.3.5 with commit 3eac7cf352cedd05215bdc7e9786c3ee4b4b43b2 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 7.4-rc2 with commit f9a11716c8445b496e9fafeec7e8412d384d02e2 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-99774 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: include/net/espintcp.h net/xfrm/espintcp.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/6653f281a84dfc050042b837fbf0a1ab87f8f645 https://git.kernel.org/stable/c/d50065a04b8b2edd9215a1960a48c4a4667a5b8c https://git.kernel.org/stable/c/3eac7cf352cedd05215bdc7e9786c3ee4b4b43b2 https://git.kernel.org/stable/c/f9a11716c8445b496e9fafeec7e8412d384d02e2