From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 699622C08DB for ; Thu, 3 Jul 2025 08:14:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751530450; cv=none; b=sSJWA3596GBBRcICJZ0mqW+IGIAkuJJPqclPMUEGrOjzaG3rwFe/kXethaRauCZtMPKr6CZt1Y1LRWCQG5BONpVov8jtE4neqg6ym328FNIrfDKlUNIAnvyBdY3E2Pn/gj7FTLwZFbLH5b2VtVf72fcYJ3xzBEDD3iWOc0nn3ig= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751530450; c=relaxed/simple; bh=5fgqAFoHpevdwnt+tWW/feJhSEUrn4HY8CPlrPmM8l0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=g0lYbNt2Ss7ZoKE5meGDPe7vsGKaaU8EWJVvAq+mDJ0Ayfnjp180jxwGO7tsbBAYA2kRbD0cEqDqcg/wZ6MCK6sKTzoE6xvP5fej8uUxWvVbRHjyMuWsVPwfgv2Q7brFQECgJ20Rfwbj2GBMwXWq26lBW1XE4aqbKudaZAyqZ2c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=XBbHbYbQ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="XBbHbYbQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 70A0EC4CEE3; Thu, 3 Jul 2025 08:14:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1751530449; bh=5fgqAFoHpevdwnt+tWW/feJhSEUrn4HY8CPlrPmM8l0=; h=From:To:Cc:Subject:Date:Reply-to:From; b=XBbHbYbQBXRVVK/DuyozAJWUdEiaEliibcdRoijTg++KTHdB73if3l38NGmaMnph1 1m7pENFj4KHnpN5/HQ91YdIH4KOZ0bkb4tPwqu/RxGJVnliP6N+qEbaD95WcdC2aPk s1cU67SJsjjuaiSdYZkufHSvBnb5UTv65L3mvINQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2025-38097: espintcp: remove encap socket caching to avoid reference leak Date: Thu, 3 Jul 2025 10:14:05 +0200 Message-ID: <2025070305-CVE-2025-38097-287c@gregkh> X-Mailer: git-send-email 2.50.0 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3367; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ZxY3uLo5l6UoRMG4MpD2AFdqOlFUvxjo9Qf6xVJUlbQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDBlp1mcPsshPTD08+Wtm+DO51bzCyk8fV2V/MLZ142c8y LGw8tzUjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZiI/xKG+RneqdUnbbQbXx04 dP/Popeqm75MmcuwYI/P8071fvE036mCWQ9t3Cwzrz2MAgA= 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: espintcp: remove encap socket caching to avoid reference leak The current scheme for caching the encap socket can lead to reference leaks when we try to delete the netns. The reference chain is: xfrm_state -> enacp_sk -> netns Since the encap socket is a userspace socket, it holds a reference on the netns. If we delete the espintcp state (through flush or individual delete) before removing the netns, the reference on the socket is dropped and the netns is correctly deleted. Otherwise, the netns may not be reachable anymore (if all processes within the ns have terminated), so we cannot delete the xfrm state to drop its reference on the socket. This patch results in a small (~2% in my tests) performance regression. A GC-type mechanism could be added for the socket cache, to clear references if the state hasn't been used "recently", but it's a lot more complex than just not caching the socket. The Linux kernel CVE team has assigned CVE-2025-38097 to this issue. Affected and fixed versions =========================== Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.1.141 with commit e4cde54b46a87231c77256a633be1bef62687d69 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.6.93 with commit b58a295d10065960bcb9d60cb8ca6ead9837cd27 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.12.31 with commit 9cbca30102028f9ad3d2098f935c4368f581fd07 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.14.9 with commit 74fd327767fb784c5875cf7c4ba1217f26020943 Issue introduced in 5.6 with commit e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and fixed in 6.15 with commit 028363685bd0b7a19b4a820f82dd905b1dc83999 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-2025-38097 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/xfrm.h net/ipv4/esp4.c net/ipv6/esp6.c net/xfrm/xfrm_state.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/e4cde54b46a87231c77256a633be1bef62687d69 https://git.kernel.org/stable/c/b58a295d10065960bcb9d60cb8ca6ead9837cd27 https://git.kernel.org/stable/c/9cbca30102028f9ad3d2098f935c4368f581fd07 https://git.kernel.org/stable/c/74fd327767fb784c5875cf7c4ba1217f26020943 https://git.kernel.org/stable/c/028363685bd0b7a19b4a820f82dd905b1dc83999