Answer in brief
CVE-2025-38097 records a High severity (CVSS 7.8) vulnerability in espintcp: remove encap socket caching to avoid reference leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc7:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <e4cde54b46a87231c77256a633be1bef62687d69 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <b58a295d10065960bcb9d60cb8ca6ead9837cd27 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <9cbca30102028f9ad3d2098f935c4368f581fd07 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <74fd327767fb784c5875cf7c4ba1217f26020943 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <028363685bd0b7a19b4a820f82dd905b1dc83999 | e4cde54b46a87231c77256a633be1bef62687d69, b58a295d10065960bcb9d60cb8ca6ead9837cd27, 9cbca30102028f9ad3d2098f935c4368f581fd07, 74fd327767fb784c5875cf7c4ba1217f26020943, 028363685bd0b7a19b4a820f82dd905b1dc83999 |
| Linux/Linuxgeneric | 5.6 | Not reported |
| Linux/Linuxgeneric | >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <e32bafd08ee35feacd47b05cc5bfe9cd9659cd25 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <9673ca00e6c5503069dc98780e2e89db0e663c16 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <e4cde54b46a87231c77256a633be1bef62687d69 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <b58a295d10065960bcb9d60cb8ca6ead9837cd27 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <9cbca30102028f9ad3d2098f935c4368f581fd07 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <74fd327767fb784c5875cf7c4ba1217f26020943 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <028363685bd0b7a19b4a820f82dd905b1dc83999 | e32bafd08ee35feacd47b05cc5bfe9cd9659cd25, 9673ca00e6c5503069dc98780e2e89db0e663c16, e4cde54b46a87231c77256a633be1bef62687d69, b58a295d10065960bcb9d60cb8ca6ead9837cd27, 9cbca30102028f9ad3d2098f935c4368f581fd07, 74fd327767fb784c5875cf7c4ba1217f26020943, 028363685bd0b7a19b4a820f82dd905b1dc83999 |
Published upstream
Jul 3, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.