LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22037: ksmbd: fix null pointer dereference in alloc_preauth_hash()

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix null pointer dereference in alloc_preauth_hash() The Client send malformed smb2 negotiate request. ksmbd return error response. Subsequently, the client can send smb2 session setup even thought conn->preauth_info is not allocated. This patch add KSMBD_SESS_NEED_SETUP status of connection to ignore session setup request if smb2 negotiate phase is not complete.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A remote, unauthenticated client can crash a Linux system’s ksmbd file-sharing service by sending malformed SMB requests in an unexpected sequence. The primary impact is service or system availability; the supplied evidence does not indicate data theft or modification.

Executive priority

Treat this as a high-priority availability issue for reachable ksmbd servers, especially business-critical file-sharing systems. Patch promptly through supported kernel channels and reduce SMB exposure while updates are pending. Systems not using ksmbd are unlikely to be exposed to this specific flaw.

Technical view

A malformed SMB2 negotiate request can leave conn->preauth_info unallocated. A subsequent session-setup request reaches alloc_preauth_hash() and triggers a null-pointer dereference. The kernel fix introduces KSMBD_SESS_NEED_SETUP state handling, rejecting session setup until negotiation completes. CVSS 3.1 is 7.5: network-accessible, low complexity, unauthenticated, availability-only impact.

Likely exposure

Exposure requires Linux systems running ksmbd and accepting SMB connections from an attacker-controlled network. Internet-facing or broadly reachable SMB services warrant the fastest review. The supplied affected-version data is ambiguous, so determine exposure through vendor kernel guidance and fix-commit inclusion rather than version strings alone.

Exploitation context

The supplied record is not in CISA KEV, and the provided sources do not establish active exploitation. The network-accessible, unauthenticated denial-of-service condition is nevertheless practical enough to prioritize wherever ksmbd is reachable. No evidence supplied supports confidentiality or integrity impact.

Researcher notes

The affected-version entries in the supplied record contain duplicates, a value of “0,” and unclear boundaries. Avoid deriving precise vulnerable ranges from them. The core defect and correction are well described, but exploit prevalence is unsupported. Validate backports by commit or vendor advisory, not kernel version comparison alone.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix for CVE-2025-22037.
  • Check distribution or appliance guidance because the supplied version boundaries are ambiguous.
  • Disable ksmbd where SMB file sharing is unnecessary.
  • Until patched, restrict SMB access to trusted networks and required clients only.

Validation and detection

  • Inventory systems loading or running ksmbd and record their kernel package versions.
  • Identify which ksmbd services are reachable from untrusted or internet-connected networks.
  • Confirm the installed kernel includes the applicable referenced stable commit or vendor backport.
  • Review kernel and service logs for ksmbd crashes or null-pointer faults.
  • After updating, verify ksmbd operates normally and the intended SMB access restrictions remain enforced.
Prepared
Confidence
medium
Sources
8

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-22037 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-22037Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cfunaffected
LinuxLinux5.15, 0, 6.6.107, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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