LiveActive security incident?Get immediate response
CVE Record

CVE-2025-37962: ksmbd: fix memory leak in parse_lease_state()

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix memory leak in parse_lease_state() The previous patch that added bounds check for create lease context introduced a memory leak. When the bounds check fails, the function returns NULL without freeing the previously allocated lease_ctx_info structure. This patch fixes the issue by adding kfree(lreq) before returning NULL in both boundary check cases.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in the ksmbd SMB server code. A failed bounds check can leave an allocated structure unfreed. The provided sources do not give CVSS, CWE, exploitability, or impact details beyond the leak, so urgency depends on whether affected kernels and ksmbd are present.

Executive priority

Treat this as a patch-management item, not an emergency, unless ksmbd exposure is confirmed on important systems. The current public evidence lacks severity scoring and exploitation claims.

Technical view

CVE-2025-37962 fixes a leak in ksmbd parse_lease_state(). After a prior bounds-check change, two failure paths returned NULL without freeing lease_ctx_info. The kernel fix adds kfree(lreq) before those returns. Public sources identify Linux stable commits and a Debian LTS advisory, but not exploit prerequisites or confirmed impact severity.

Likely exposure

Exposure is most likely on Linux systems running kernels that include the vulnerable ksmbd change and use the kernel SMB server path. The supplied version data is incomplete and should not be treated as a full affected-range statement.

Exploitation context

The source bundle does not show active exploitation, public exploit code, or KEV listing. It only describes a memory leak triggered when create lease context bounds checks fail in ksmbd.

Researcher notes

Focus review on ksmbd create lease context parsing and the two bounds-check failure paths in parse_lease_state(). Evidence supports a memory leak fix only; further impact analysis requires kernel configuration, reachable code path, and vendor backport status.

Mitigation direction

  • Apply vendor Linux kernel updates containing the referenced stable fixes.
  • Check Debian LTS and your distribution advisories for package-specific fixed versions.
  • Prioritize systems where ksmbd is enabled or SMB service is exposed.
  • If no vendor fix is available, follow vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify systems with ksmbd enabled or packaged for SMB serving.
  • Compare installed kernels against vendor advisories and referenced stable commits.
  • Confirm vulnerability scanner findings with distribution package changelogs.
  • Document any exposed SMB services for prioritization.
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-37962 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
1ADP 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.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux629dd37acc336ad778979361c351e782053ea284, 60b7207893a8a06c78441934931a08fdad63f18e, 800c482c9ef5910f05e3a713943c67cc6c1d4939, 9a1b6ea955e6c7b29939a6d98701202f9d9644ec, bab703ed8472aa9d109c5f8c1863921533363dae, a41cd52f00907a040ca22c73d4805bb79b0d0972, 6.13.11unaffected
LinuxLinux6.1.134, 6.6.87, 6.12.23, 6.14.2unaffected
Weakness

CWE details

No CWE listed

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