LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71220: smb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()

In the Linux kernel, the following vulnerability has been resolved: smb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe() When ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel ksmbd SMB server bug in error handling. The public record says a session RPC close call was missing when a response pinning operation fails. Business urgency is hard to rank because the bundle provides no CVSS score, CWE, impact statement, or exploitation evidence.

Executive priority

Treat this as a targeted kernel hygiene item for environments using Linux ksmbd. It should be scheduled into normal kernel patching unless local exposure is high, because impact and exploitation evidence are not established in the provided sources.

Technical view

In create_smb2_pipe(), if ksmbd_iov_pin_rsp() fails, the resolved kernel fix calls ksmbd_session_rpc_close() on that error path. The source bundle does not state whether the missing cleanup causes denial of service, resource leakage, privilege impact, or another consequence.

Likely exposure

Exposure is most relevant to Linux systems using the in-kernel ksmbd SMB server on affected kernel builds. Systems not running ksmbd are less likely to be exposed. The affected-version data is limited, so distribution-specific kernel advisories and backport status matter.

Exploitation context

The bundle marks KEV as false and provides no cited source claiming active exploitation or public exploit availability. It only documents a kernel fix and affected version metadata, so exploitation practicality cannot be concluded from the supplied evidence.

Researcher notes

Focus analysis on the ksmbd create_smb2_pipe() error path and cleanup semantics around ksmbd_iov_pin_rsp() failure. The record names the missing ksmbd_session_rpc_close() call but does not define a security impact, trigger conditions, or exploit status.

Mitigation direction

  • Identify Linux hosts running or loading ksmbd.
  • Apply kernel updates containing the referenced stable fixes when available.
  • Check distribution advisories for backported fixes and exact package versions.
  • Disable ksmbd where it is not required.
  • Restrict SMB exposure to trusted networks where operationally possible.

Validation and detection

  • Inventory kernel versions across Linux servers and appliances.
  • Confirm whether the ksmbd module or service is enabled.
  • Compare installed kernel packages against vendor fixed versions or backport notes.
  • Review SMB listening exposure on affected hosts.
  • Track the referenced kernel stable commits in package changelogs.
Prepared
Confidence
medium
Sources
8

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-71220 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
7Source 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
LinuxLinuxf2283680a80571ca82d710bc6ecd8f8beac67d63, 9f297df20d93411c0b4ddad7f88ba04a7cd36e77, e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d, e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d, e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d, e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d, 5.15.145, 6.1.71unaffected
LinuxLinux6.6, 0, 5.15.200, 6.1.163, 6.6.124, 6.12.70, 6.18.10, 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.