LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22038: ksmbd: validate zero num_subauth before sub_auth is accessed

In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate zero num_subauth before sub_auth is accessed Access psid->sub_auth[psid->num_subauth - 1] without checking if num_subauth is non-zero leads to an out-of-bounds read. This patch adds a validation step to ensure num_subauth != 0 before sub_auth is accessed.

HighCVSS 8.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux's ksmbd SMB server can read beyond intended memory when processing a security identifier with zero sub-authorities. An authenticated network user could potentially expose data, cause limited modification, or disrupt service. Systems not using ksmbd are less likely to be exposed.

Executive priority

Treat as a high-priority kernel update for reachable ksmbd servers, especially where many authenticated users can connect. Prioritize exposure discovery immediately, then patch according to distribution guidance. Hosts without ksmbd use are lower priority after configuration is verified.

Technical view

When num_subauth is zero, ksmbd accesses sub_auth[num_subauth - 1], producing an out-of-bounds read. The correction validates that num_subauth is nonzero before access. CVSS 3.1 rates it 8.3: network-accessible, low complexity, low privileges, no user interaction, with high confidentiality and availability impact.

Likely exposure

Highest exposure is on affected Linux systems running ksmbd with SMB reachable by untrusted or broadly authorized clients. Exploitation requires low privileges. The supplied version data is ambiguous, so determine exposure through distribution advisories and whether the installed kernel contains the applicable stable fix.

Exploitation context

The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. That absence does not prove exploitation is impossible. The network attack vector, low complexity, and low privilege requirement make exposed ksmbd servers important to remediate.

Researcher notes

CWE-125 applies. The fault is an index underflow leading to an out-of-bounds read when num_subauth equals zero. Stable-tree corrections are referenced for multiple branches. The supplied affected-version array is not sufficiently clear for precise package decisions; use commit containment and distribution package advisories.

Mitigation direction

  • Install a distribution-supported kernel update containing the applicable referenced stable fix.
  • Follow the Linux distribution's advisory for package-specific fixed versions and reboot requirements.
  • Until updated, restrict ksmbd SMB reachability to necessary, trusted clients.
  • Prioritize hosts exposing ksmbd across internet-facing or broadly accessible networks.

Validation and detection

  • Inventory running kernel versions and identify systems configured to use ksmbd.
  • Confirm whether SMB backed by ksmbd is reachable from untrusted network segments.
  • Map installed kernels to distribution advisories or the referenced stable commits.
  • After updating, verify the host booted into the corrected kernel.
  • Reassess network exposure and confirm vulnerability findings no longer reproduce.
Prepared
Confidence
medium
Sources
9

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.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-22038 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
8.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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.

2CVSS vectors
3Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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
8.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H2.85.5Linux
7.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

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

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.