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 00EF53B6361 for ; Fri, 4 Sep 2026 16:00:11 +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=1788537613; cv=none; b=MGsLDhMQ18OStPrPucrZDWuqL8EybjPzjRuVEet6XECGiVo+hIqRebXR07qY8NQFQT5vcol5aWZWbNgAXzQ0zYUyljnbYNvFKxMpBmdlqvg6Kq2zWOyCmSx9/DxaDs2uj6xlSqiPSmProEqaHr5MD/qnL9+f2IzLt8/cgnmazes= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788537613; c=relaxed/simple; bh=Ey3nY0I3JrIc3e3e7EZdnlXPIPsVDqXGgvoWiY+Hoa4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=XDyhO/y0k8qnvq3OeDC4gG5sNxb8QSXMwXiP+OCIN6COeS+vZLpv2CbaFoHzxYnYU/Ma606dZENeHx2FViYhTLfO56bQSNYsah+Y2q3W3IZzicUMmS62mByxWxsWOSLKhA/4HNDFc+pxYtulgQUvIerTBrhGAh/UmyYYUIKxTxM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=azeQtDpt; 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="azeQtDpt" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EF8561F00ADB; Fri, 4 Sep 2026 16:00:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788537611; bh=QbeQ1b2qNG761lRhxV9xC7LjPEiSDsdQOrB/XPZ/MF0=; h=From:To:Cc:Subject:Date:Reply-To; b=azeQtDptRpHGU2hY+rLz1WKpHBsbtwYjyK1m78WR4f4WtXRRlr2OxqpRe08tDskUV 9jETTQvifXrkaeeJUbLw/wkCds3b4yeyIBiYAcrK4zEv1wsfP3iLwOBfwaL0m7uG6p UDMZSdJ9PDXGEykGH8VjnSMtmHdqSJJn4sagFTss= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80845: xfrm: avoid lock inversion in nat keepalive work Date: Fri, 4 Sep 2026 17:53:12 +0200 Message-ID: <2026090459-CVE-2026-80845-aea7@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=3125; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=vqqFOQfxG9njgfkvFZ0SIEQgtcDzm4EQYCUCSNmq9sQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmzXkYH91gdSAhXv7pKlzmj/PjWSznaszbpvL4zy7Z2X 3fo5m12HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjARMWuGBTNfeJwy9WFJP/Gv Wvibxod1Sn9jJjMs6Dgwc4rR6g+9hzVfciULONf53H3iDgA= 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: avoid lock inversion in nat keepalive work nat_keepalive_work() walks the state table while xfrm_state_walk() holds net->xfrm.xfrm_state_lock. Its callback then acquires x->lock, which conflicts with the delete path taking the same locks in reverse order via xfrm_state_delete() and __xfrm_state_delete(). This creates an AB-BA deadlock that is reported by lockdep when a NAT keepalive worker races with SA deletion. Fix this by splitting the keepalive walk into two phases. First, collect the candidate states while the walk holds xfrm_state_lock and take a reference on each state. Then, after the walk completes, process each collected state and acquire x->lock without nesting it under xfrm_state_lock. The Linux kernel CVE team has assigned CVE-2026-80845 to this issue. Affected and fixed versions =========================== Issue introduced in 6.11 with commit f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae and fixed in 6.12.108 with commit ea09210462316e5235a25eccb11ad0708d86615e Issue introduced in 6.11 with commit f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae and fixed in 6.18.49 with commit 5c86c895d1cac81a71ead3005084c6265cf6a7a5 Issue introduced in 6.11 with commit f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae and fixed in 7.1.13 with commit 89ef3a2e1e4682ab82b0455ce113f8c39fb9e50d Issue introduced in 6.11 with commit f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae and fixed in 7.2.3 with commit a9fa05b7a1246797748d15771052639e0d3cabf1 Issue introduced in 6.11 with commit f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae and fixed in 7.3-rc1 with commit 763fe700b7c58ad64fe5202c5638848244dd4127 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-80845 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_nat_keepalive.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/ea09210462316e5235a25eccb11ad0708d86615e https://git.kernel.org/stable/c/5c86c895d1cac81a71ead3005084c6265cf6a7a5 https://git.kernel.org/stable/c/89ef3a2e1e4682ab82b0455ce113f8c39fb9e50d https://git.kernel.org/stable/c/a9fa05b7a1246797748d15771052639e0d3cabf1 https://git.kernel.org/stable/c/763fe700b7c58ad64fe5202c5638848244dd4127