CVE-2025-38097

espintcp: remove encap socket caching to avoid reference leak

MEDIUM
5.5
CVSS Score
Published: July 3, 2025 at 08:13 AM UTC
Updated: October 15, 2026 at 10:18 PM UTC
2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.6 ≤ v < 6.1.1416.13 ≤ v < 6.14.96.2 ≤ v < 6.6.936.7 ≤ v < 6.12.316.156.15 rc16.15 rc26.15 rc36.15 rc46.15 rc56.15 rc66.15 rc7e27cca96cd68fa2c6814c90f9a1cfd36bb68c593
Vendor states this is fixed in 028363685bd0b7a19b4a820f82dd905b1dc83999 (fixed)
Vendor states this is fixed in 74fd327767fb784c5875cf7c4ba1217f26020943 (fixed)
Vendor states this is fixed in 9673ca00e6c5503069dc98780e2e89db0e663c16 (fixed)
Vendor states this is fixed in 9cbca30102028f9ad3d2098f935c4368f581fd07 (fixed)
Vendor states this is fixed in b58a295d10065960bcb9d60cb8ca6ead9837cd27 (fixed)
Vendor states this is fixed in e32bafd08ee35feacd47b05cc5bfe9cd9659cd25 (fixed)
Vendor states this is fixed in e4cde54b46a87231c77256a633be1bef62687d69 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.141 (unaffected)
Vendor states this is fixed in 6.12.31 (unaffected)
Vendor states this is fixed in 6.14.9 (unaffected)
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.6.93 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-Other

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card