LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3865: ksmbd: fix out-of-bound read in smb2_write

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix out-of-bound read in smb2_write ksmbd_smb2_check_message doesn't validate hdr->NextCommand. If ->NextCommand is bigger than Offset + Length of smb2 write, It will allow oversized smb2 write length. It will cause OOB read in smb2_write.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A remote user with limited privileges may be able to make Linux's ksmbd SMB server read beyond intended memory boundaries. This creates potential data-disclosure and service-disruption risk. Exposure is limited to systems using affected kernels with ksmbd enabled and reachable.

Executive priority

Treat this as a high-priority, targeted kernel remediation. Promptly identify internet-facing or broadly reachable ksmbd servers and patch them first. The absence of cited active exploitation lowers emergency pressure, but the potential confidentiality and availability impact warrants timely action.

Technical view

ksmbd_smb2_check_message fails to validate the SMB2 NextCommand value against the write Offset and Length. An oversized value can therefore permit an excessive SMB2 write length, leading smb2_write to perform an out-of-bounds read. The supplied CVSS 3.1 score is 8.1, reflecting high confidentiality and availability impact.

Likely exposure

Prioritize Linux systems running ksmbd and accepting SMB connections. The bundle lists 5.15, 5.15.121, 6.1.36, 6.3.10, and 6.4 as affected, but its version data contains ambiguities. Confirm exact affected and fixed package boundaries with the applicable Linux distributor.

Exploitation context

The supplied record does not list this CVE in CISA KEV and provides no cited evidence of public or active exploitation. The CVSS vector indicates network access, low complexity, low privileges, and no user interaction, but that describes theoretical exploit conditions rather than observed attacks.

Researcher notes

The defect concerns validation of a compound SMB2 message boundary, specifically NextCommand relative to write Offset and Length. Four stable-kernel commits are referenced as fixes. The supplied version representation is insufficient for reliable distribution-level package decisions, and no CWE, exploit details, or attack telemetry are provided.

Mitigation direction

  • Update to a distribution-supported kernel confirmed to contain the referenced ksmbd fix.
  • Check Linux distributor guidance for exact fixed packages and reboot requirements.
  • Prioritize remediation where ksmbd is enabled and reachable from untrusted networks.
  • Consider temporarily restricting unneeded ksmbd access after reviewing operational dependencies.

Validation and detection

  • Inventory active kernel versions and identify systems where ksmbd is enabled.
  • Determine whether affected ksmbd services accept connections from untrusted networks.
  • Compare kernel package changelogs against distributor guidance and the referenced fix commits.
  • After updating, verify the fixed kernel is running following any required reboot.
Prepared
Confidence
medium
Sources
6

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-2023-3865 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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
5Source 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
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H2.85.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2023-3865Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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, 0626e6641f6b467447c81dd7678a69c66f7746cfunaffected
LinuxLinux5.15, 0, 5.15.121, 6.1.36, 6.3.10, 6.4affected
Weakness

CWE details

No CWE listed

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