LiveActive security incident?Get immediate response
CVE Record

CVE-2023-4130: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using ->NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malformed SMB extended-attribute request can cause Linux's ksmbd server to access memory outside the intended buffer. The supplied severity data indicates possible kernel-data exposure or system failure. Only systems using ksmbd on an affected kernel are exposed; ordinary Linux systems without this service are not affected through this path.

Executive priority

Prioritize prompt remediation on reachable ksmbd servers, especially those accessible by untrusted users or networks. Systems without ksmbd have substantially lower urgency for this specific flaw. The high CVSS score supports accelerated patching, although the supplied evidence does not justify claiming an active exploitation emergency.

Technical view

smb2_set_ea() follows NextEntryOffset while processing multiple FILE_FULL_EA_INFORMATION entries. It validated the next entry using the current entry's offset rather than the total buffer length, permitting out-of-bounds access. CVSS 3.1 scores this 8.1: network-accessible, low complexity, low privileges, no user interaction, with high confidentiality and availability impact.

Likely exposure

Exposure is limited to systems running ksmbd on an affected Linux kernel. The supplied version data references 5.15 and several 6.x points but does not clearly define downstream package ranges. Confirm remediation through distribution backport information or inclusion of the applicable stable-kernel commit.

Exploitation context

The bundle does not list this CVE in KEV, and no supplied source establishes active exploitation or a public exploit. The CVSS vector indicates a network attacker with low privileges could attempt exploitation without user interaction. Actual reachability depends on ksmbd being active and accessible to the attacker.

Researcher notes

The source describes incorrect bounds validation but supplies no CWE or confirmed exploitation evidence. Four stable commits appear to cover different maintained kernel branches; applicability must be matched to the deployed branch or downstream backport. The supplied affected-version array is ambiguous, so do not infer safety from version numbers alone.

Mitigation direction

  • Upgrade to a vendor-supported kernel release containing the applicable upstream stable fix.
  • Confirm your distribution's kernel package backports one of the cited stable commits.
  • Until updated, restrict ksmbd access to trusted networks and accounts, following vendor guidance.
  • Disable ksmbd where the kernel SMB server is not operationally required.

Validation and detection

  • Determine whether ksmbd is enabled, loaded, and accepting SMB connections.
  • Record exact kernel and distribution package versions across reachable hosts.
  • Verify the running kernel includes the applicable stable commit or distributor backport.
  • Identify low-privileged accounts and networks able to reach each ksmbd service.
  • Review kernel logs for ksmbd faults; their absence does not establish non-exposure.
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-4130 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-4130Attack 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.127, 6.1.46, 6.4.11, 6.5affected
Weakness

CWE details

No CWE listed

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