LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53358: ksmbd: fix racy issue under cocurrent smb2 tree disconnect

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix racy issue under cocurrent smb2 tree disconnect There is UAF issue under cocurrent smb2 tree disconnect. This patch introduce TREE_CONN_EXPIRE flags for tcon to avoid cocurrent access.

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-53358 is a Linux kernel use-after-free bug in ksmbd during concurrent SMB2 tree disconnect handling. If a vulnerable kernel is running ksmbd, a low-privileged local attacker could potentially affect confidentiality, integrity, and availability. The source bundle does not show public exploitation or KEV listing.

Executive priority

Treat as high priority for Linux servers that expose ksmbd and allow non-admin local access. It is less urgent for systems without ksmbd enabled or without untrusted local users, but kernel maintenance teams should still track vendor fixes.

Technical view

The flaw is a race in ksmbd tree connection teardown. Concurrent SMB2 tree disconnect activity can cause use-after-free, classified as CWE-416. The kernel fix adds TREE_CONN_EXPIRE state to prevent concurrent access to an expiring tree connection. CVSS 3.1 is 7.0 with local attack vector, high complexity, and low privileges required.

Likely exposure

Exposure is most relevant to Linux systems running affected kernels with ksmbd SMB server functionality enabled. The affected version data includes Linux 5.15 and later listed kernel lines through 6.4, but the bundle does not map those cleanly to distribution packages.

Exploitation context

No active exploitation is cited. KEV is false in the bundle. The CVSS vector indicates exploitation requires local access, low privileges, no user interaction, and high attack complexity, so urgency depends heavily on whether untrusted users can access affected hosts.

Researcher notes

The public bundle provides the root cause and stable commit references, but not distribution-specific package status or exploit telemetry. Validation should focus on ksmbd presence, kernel lineage, and whether the relevant stable fix is included in deployed kernels.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check your Linux distribution advisory for exact fixed package versions.
  • Disable ksmbd where kernel SMB service is not required.
  • Limit low-privileged local access on systems running vulnerable kernels.

Validation and detection

  • Inventory systems running Linux kernels in the affected version ranges.
  • Confirm whether ksmbd is enabled or loaded on those systems.
  • Map installed kernel packages to vendor fixed versions or stable commits.
  • Prioritize hosts with untrusted local users or shared access.
Prepared
Confidence
medium
Sources
7

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-416: 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-2023-53358 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 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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
1ADP providers
6Source links

SSVC decision data

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

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
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cf, 0626e6641f6b467447c81dd7678a69c66f7746cfunaffected
LinuxLinux5.15, 0, 5.15.145, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.