Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38097: espintcp: remove encap socket caching to avoid reference leak

MediumCVSS 5.5 · v3.1—No exploit Fix available

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

JSON

Action score

22

Monitor

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.

Follow CVE-2025-38097

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux kernel
debiandebian 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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.7.1.el10_26.12.0-211.7.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38095Jul 3, 2025 · dma-buf: insert memory barrier before updating num_fences
    22Monitor
  • ← EarlierCVE-2025-38096Jul 3, 2025 · wifi: iwlwifi: don't warn when if there is a FW error
    22Monitor
  • Later →CVE-2025-38099Jul 3, 2025 · Bluetooth: Disable SCO support if READ_VOICE_SETTING is unsupported/broken
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux028363685bd0b7a19b4a820f82dd905b1dc83999Vendor (CNA)
Linux Linux74fd327767fb784c5875cf7c4ba1217f26020943Vendor (CNA)
Linux Linux9673ca00e6c5503069dc98780e2e89db0e663c16Vendor (CNA)
Linux Linux9cbca30102028f9ad3d2098f935c4368f581fd07Vendor (CNA)
Linux Linuxb58a295d10065960bcb9d60cb8ca6ead9837cd27Vendor (CNA)
Linux Linuxe32bafd08ee35feacd47b05cc5bfe9cd9659cd25Vendor (CNA)
Linux Linuxe4cde54b46a87231c77256a633be1bef62687d69Vendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.7.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.147-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2Package 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.

References

All records