LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71148: net/handshake: restore destructor on submit failure

In the Linux kernel, the following vulnerability has been resolved: net/handshake: restore destructor on submit failure handshake_req_submit() replaces sk->sk_destruct but never restores it when submission fails before the request is hashed. handshake_sk_destruct() then returns early and the original destructor never runs, leaking the socket. Restore sk_destruct on the error path.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-71148 is a Linux kernel bug where a failed networking handshake request can leave a socket cleanup handler unrestored. That can leak sockets instead of freeing them. The public record does not provide CVSS, impact scoring, or evidence of active exploitation.

Executive priority

Treat as a kernel maintenance item pending vendor severity. Prioritize normal patch cycles, with higher urgency for shared, high-availability, or internet-facing Linux infrastructure where resource leaks could affect service reliability.

Technical view

In net/handshake, handshake_req_submit() replaces sk->sk_destruct. If submission fails before the request is hashed, the original destructor was not restored. handshake_sk_destruct() could then return early, preventing normal socket cleanup and causing a socket leak. Upstream stable commits restore sk_destruct on the error path.

Likely exposure

Exposure is limited to Linux systems running affected kernel code paths for net/handshake. The bundle lists Linux kernel versions and upstream commits, but exact downstream distro exposure must be confirmed against vendor kernel packages.

Exploitation context

No provided source states active exploitation, public weaponization, or CISA KEV listing. The described impact is a resource leak on an error path, not confirmed code execution or privilege escalation.

Researcher notes

The source evidence identifies the bug and fix but omits CVSS, CWE, exploitability analysis, and downstream package mapping. Further assessment should focus on reachable net/handshake error paths and distro-specific backports, without assuming broader impact.

Mitigation direction

  • Apply the relevant vendor kernel update when available.
  • Use upstream stable fixes only through approved kernel maintenance processes.
  • Prioritize systems running affected Linux kernels in exposed or multi-tenant roles.
  • Monitor Linux distribution advisories for exact fixed package versions.
  • Reboot or live-patch as required for the kernel fix to take effect.

Validation and detection

  • Inventory deployed Linux kernel versions and package build identifiers.
  • Compare kernels against the CVE record and vendor advisories.
  • Confirm whether the upstream stable fix is present in deployed source or packages.
  • Review monitoring for abnormal socket or kernel resource growth.
  • Track remediation status until patched kernels are running.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71148 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3b3009ea8abb713b022d94fba95ec270cf6e7eae, 3b3009ea8abb713b022d94fba95ec270cf6e7eae, 3b3009ea8abb713b022d94fba95ec270cf6e7eae, 3b3009ea8abb713b022d94fba95ec270cf6e7eaeunaffected
LinuxLinux6.4, 0, 6.6.120, 6.12.64, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.