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 551C63CF02D for ; Fri, 4 Sep 2026 16:00:15 +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=1788537617; cv=none; b=BlcOASuo5TdW9oguM+UxiiVYkRPZ8X8uyigrFY23ofxXmygC7Xklt1VMmvTCBZ4ftRfTdfkIVcqmkbrqrT42rXvwq0xAjZmNsyyskDufP3BOONlslqb+WgO5609c6a0TiOmmItZRL1jTDZQubaluNbV/IJDLMuc7wZxRAArJMco= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788537617; c=relaxed/simple; bh=/5ehJv6aW6RlsxWu4sIZ3o2ZazySxS5ObWsKo4kBhdc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=MLOw2dUw9fjVUYa1C3RnB8M5LSBKrG6O6ymOnY+Gr1zNnQu8gVdrdRUfNs0DpnrR4tVW21ALIkE/B6ySS68EkuyKSO7LxTMPk2kgolbyA+qrFtPJqFCVeUHelUiJ8fURwVDEE45X7IV26sebKbJRlxh8lb2rnnIeUZxT9AYCnPM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=KNxC94VA; 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="KNxC94VA" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 124711F00AC4; Fri, 4 Sep 2026 16:00:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788537615; bh=5YTWns4mkT4tIO4kbvrHhMKUE1JK05r/F4JGiV0LboU=; h=From:To:Cc:Subject:Date:Reply-To; b=KNxC94VALIOOsu+mSHHq20+8hfqlPaBaxUkor/AfIp1U30CrJOU6vAddiWa5PnHev IYpTnxRoPh4jF+5KP7DeqYbLkGPKHQGiloeOY2EXzjlPbnjDsCZYxQp2nah+r3mYfJ I0QfvRnfdmYhbw2DplIbyNIvddgduYoU4xcyPUCc= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80846: xfrm: drop ESP-in-TCP packets with no ingress device Date: Fri, 4 Sep 2026 17:53:13 +0200 Message-ID: <2026090459-CVE-2026-80846-8755@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=4108; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=+Vz97g6mTPaiIU0bOmckVO73AMDvlVgGJTpXasWa2g4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmzXkavf7lkQmBG1MSI9awrHXdmm2nsm/Fl1syMv5I59 6Usn3QzdMSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEFm5mWDBhsvbEG1vauOVZ bhgGaR17d/H7k2SG+YEqD50PivdbqnV+tit0Swo58EvnMwA= 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: drop ESP-in-TCP packets with no ingress device ESP-in-TCP receives records through the TCP strparser. handle_esp() restores skb->dev from the saved skb_iif before passing the packet into the XFRM input path. Queued TCP data can be processed after the original ingress device has been removed, for example during veth or net namespace teardown. In that case dev_get_by_index_rcu() returns NULL. The XFRM IPv4 and IPv6 input paths both expect skb->dev to be valid while building the route lookup, so queued ESP-in-TCP data can dereference a NULL device. Drop the packet if the saved ingress device can no longer be resolved. Such a packet can no longer be routed through the normal XFRM receive path, and this preserves the existing behaviour for packets whose ingress device still exists. The Linux kernel CVE team has assigned CVE-2026-80846 to this issue. Affected and fixed versions =========================== Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 5.10.269 with commit 239d0f71af09dc2029fd4d730cb24b8c83aaa43a Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 5.15.220 with commit f00235f9d12301183d61f75fbe4105506f3e5140 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.1.187 with commit 6af5cdb03819a5ce6e945992635c6c5e91045367 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.6.156 with commit 2dd1609cadff46c4b20ce53b91ab9cce1380456a Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.12.108 with commit c296d25efbc840be24de83f56d43bc47e714ace9 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.18.49 with commit 328e40aa774b446969c69b654c52a051a95af8a1 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 7.1.13 with commit 7911e0236616487b89db6bd3ba3f408abd10eb23 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 7.2.3 with commit 943d95233b8b4a88994e244fcf466f8c403d63f1 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 7.3-rc1 with commit e1d7c5ac1c246ce5775f604515de0a59fbf2116e 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-80846 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/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/239d0f71af09dc2029fd4d730cb24b8c83aaa43a https://git.kernel.org/stable/c/f00235f9d12301183d61f75fbe4105506f3e5140 https://git.kernel.org/stable/c/6af5cdb03819a5ce6e945992635c6c5e91045367 https://git.kernel.org/stable/c/2dd1609cadff46c4b20ce53b91ab9cce1380456a https://git.kernel.org/stable/c/c296d25efbc840be24de83f56d43bc47e714ace9 https://git.kernel.org/stable/c/328e40aa774b446969c69b654c52a051a95af8a1 https://git.kernel.org/stable/c/7911e0236616487b89db6bd3ba3f408abd10eb23 https://git.kernel.org/stable/c/943d95233b8b4a88994e244fcf466f8c403d63f1 https://git.kernel.org/stable/c/e1d7c5ac1c246ce5775f604515de0a59fbf2116e