CVE-2025-38097: espintcp: remove encap socket caching to avoid reference leak
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 028363685bd0b7a19b4a820f82dd905b1dc83999, 74fd327767fb784c5875cf7c4ba1217f26020943, 9673ca00e6c5503069dc98780e2e89db0e663c16; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 028363685bd0b7a19b4a820f82dd905b1dc83999, 74fd327767fb784c5875cf7c4ba1217f26020943, 9673ca00e6c5503069dc98780e2e89db0e663c16; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 3, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.6affected
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before e32bafd08ee35feacd47b05cc5bfe9cd9659cd25affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 9673ca00e6c5503069dc98780e2e89db0e663c16affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before e4cde54b46a87231c77256a633be1bef62687d69affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before b58a295d10065960bcb9d60cb8ca6ead9837cd27affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 9cbca30102028f9ad3d2098f935c4368f581fd07affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 74fd327767fb784c5875cf7c4ba1217f26020943affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 028363685bd0b7a19b4a820f82dd905b1dc83999affected · git
- before 5.6not affected · semver
- 5.10.270 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.6 and later · before 6.1.141
- linux linux kernel6.2 and later · before 6.6.93
- linux linux kernel6.7 and later · before 6.12.31
- linux linux kernel6.13 and later · before 6.14.9
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38095Jul 3, 2025 · dma-buf: insert memory barrier before updating num_fences22Monitor
- ← EarlierCVE-2025-38096Jul 3, 2025 · wifi: iwlwifi: don't warn when if there is a FW error22Monitor
- Later →CVE-2025-38099Jul 3, 2025 · Bluetooth: Disable SCO support if READ_VOICE_SETTING is unsupported/broken22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 028363685bd0b7a19b4a820f82dd905b1dc83999 | Vendor (CNA) |
| Linux Linux | 74fd327767fb784c5875cf7c4ba1217f26020943 | Vendor (CNA) |
| Linux Linux | 9673ca00e6c5503069dc98780e2e89db0e663c16 | Vendor (CNA) |
| Linux Linux | 9cbca30102028f9ad3d2098f935c4368f581fd07 | Vendor (CNA) |
| Linux Linux | b58a295d10065960bcb9d60cb8ca6ead9837cd27 | Vendor (CNA) |
| Linux Linux | e32bafd08ee35feacd47b05cc5bfe9cd9659cd25 | Vendor (CNA) |
| Linux Linux | e4cde54b46a87231c77256a633be1bef62687d69 | Vendor (CNA) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+3
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/74fd327767fb784c5875cf7c4ba1217f26020943
- git.kernel.org/stable/c/9673ca00e6c5503069dc98780e2e89db0e663c16
- git.kernel.org/stable/c/9cbca30102028f9ad3d2098f935c4368f581fd07
- git.kernel.org/stable/c/b58a295d10065960bcb9d60cb8ca6ead9837cd27
- git.kernel.org/stable/c/e32bafd08ee35feacd47b05cc5bfe9cd9659cd25
- git.kernel.org/stable/c/e4cde54b46a87231c77256a633be1bef62687d69
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.