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=1795154563; b=kzgTtbXeXHADbtxi1R1ECmKxDnMc/1Dax22VEMLKTkv4DgnyuTp5HsrI/b1mV1jXnFiL 2ejz7WDxVREbcwuX5rtbpuxHleCCtajr9upo4du6jwdzmlV4jmgPxj9E6sQXQuPItR3pw btR+WVbQ8qixeH7xttK1p5m19+fjDCmbvIjosSf9xcgBZpy7j1gDEMPRGcX12yOTYxyXj BigAkrLhMCA8ddY8yo/YzATJoKd8m/dDzJDBNn3uqvGybZNffvVh//NcFLDvsV3sZM9vf 8Of1A6S32iXTLAdGj7UKLss28PGaiu9h/l3MtKhKoHbAVgebdgfggVcSD2LHBhnNt+Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154563; 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=85grQFTcAQLC/bbzxe4oaFBFSaUZ09gqp1CVh8x3JFQ=; b=sS6ULcUPTvbWPmO7hpHDG1T0WWpYWJP+U+vEe1XD8GD8JpCEEZWlHiF+Zz15GgxhojgQ DMGUC7euWctaqqPKmqQ2xLdZ7hEKt2FU7d0lWo3an4Lf90UoAS58jWTxr2Az9nTEhpiRc rV3EIQ1AL+ud6XIMgby0HP9M2E0QdYGjTIYqiDtsOn4Y+a5TvIQaiBBAmrh/u19pbKo76 fjGrIXzTrd+RPCxU8bSbi/pN2ErABdR2bEp62Hdqp7ymm4Pa2nTOA4DprRrB9eiHDqiNC zSABal6d7Xg0nMwXQ/9ZifjErXmHmGLEES6gxyVBql16ji51iDzcB676FMaZiwGJ/vA== 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=kPayFzLr; 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 6E7A3606A529 for ; Fri, 20 Nov 2026 06:02:43 +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=kPayFzLr Received: by smtp.kernel.org (Postfix) with ESMTPSA id BC5721F000C6; Fri, 20 Nov 2026 06:02:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154563; bh=85grQFTcAQLC/bbzxe4oaFBFSaUZ09gqp1CVh8x3JFQ=; h=From:To:Cc:Subject:Date:Reply-To; b=kPayFzLrqrjS5LDP/Ux/axcS12sYW5vLxWEto9MWRbfjM377BM1J4REdyUYMv1ei0 SDHKUUxJNvlBqtH2Dwn7+xzrr3J88Oe9P0p6q13KgPVFKUjPNMqox5W1AIhkNV/uVC HITe0CYjOjWsFbhmvimKukRUgMTFdwBYI5SlhOJQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99786: xfrm: retry inexact policy lookup after node reinsertion Date: Fri, 20 Nov 2026 06:52:52 +0100 Message-ID: <2026112034-CVE-2026-99786-6039@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=3932; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=HLbli3DR0F21phx2YQF2SzyD4RKF8k01tk4GHScdKN8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/769iCZt95dhMbgVHX94Gxsfud9lFj9Y/ruD/sFdfM 1h169XPHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjARI1eG+U4LIs9sazyQdT00 iWt2gIMxl1usMMNc6eAZJw8+bQhe4SB4ndWDYZbHsc31AA== 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: retry inexact policy lookup after node reinsertion An inexact policy lookup first records pointers to candidate hlist heads and then traverses the lists. A concurrent policy insertion can merge inexact tree nodes between those operations: lookup policy insertion ------ ---------------- find inexact candidates save obsolete hlist head write_seqcount_begin(&bin->count) merge inexact tree nodes hlist_del_rcu(&policy->bydst) reinsert policy->bydst in survivor write_seqcount_end(&bin->count) evaluate saved candidate list miss the moved policy The merge immediately reinserts the same hlist node into the surviving tree node. RCU keeps the policy alive, but it does not provide a consistent view while its list node is moved. A lookup that selected the obsolete list can observe it empty. A lookup already traversing a moved policy can instead follow the next pointer rewritten by the reinsertion. Either case can return an incorrect IPsec policy result. The per-bin sequence counter already brackets calls to xfrm_policy_inexact_insert_node(), including node merges. The read side, however, currently validates the counter only while searching an individual rb-tree. A successful search returns without validation, and the later candidate-list traversal is outside that read-side section. Snapshot the per-bin sequence before discovering candidate heads and validate it after evaluating all candidate lists. Retry the lookup if the inexact policy tree changes while it is being searched. The Linux kernel CVE team has assigned CVE-2026-99786 to this issue. Affected and fixed versions =========================== Issue introduced in 5.0 with commit 9cf545ebd591da673bb6b6c88150212ad83567a9 and fixed in 6.12.118 with commit f10bd6c317cef7aa15e185e514513e8548f9ce77 Issue introduced in 5.0 with commit 9cf545ebd591da673bb6b6c88150212ad83567a9 and fixed in 6.18.64 with commit 6f66839895b7e9c2673df5bd9dd8d5a82033c825 Issue introduced in 5.0 with commit 9cf545ebd591da673bb6b6c88150212ad83567a9 and fixed in 7.3.5 with commit 50d8f2c52093320c70676e9f8af686ff6740abd0 Issue introduced in 5.0 with commit 9cf545ebd591da673bb6b6c88150212ad83567a9 and fixed in 7.4-rc2 with commit 868f63c8bfafa9b827168c9126f85264c39c02ec 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-99786 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: net/xfrm/xfrm_policy.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/f10bd6c317cef7aa15e185e514513e8548f9ce77 https://git.kernel.org/stable/c/6f66839895b7e9c2673df5bd9dd8d5a82033c825 https://git.kernel.org/stable/c/50d8f2c52093320c70676e9f8af686ff6740abd0 https://git.kernel.org/stable/c/868f63c8bfafa9b827168c9126f85264c39c02ec