LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54162: ksmbd: fix possible memory leak in smb2_lock()

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix possible memory leak in smb2_lock() argv needs to be free when setup_async_work fails or when the current process is woken up.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-54162 is a Linux kernel ksmbd issue where memory may not be freed in an SMB2 lock handling path. The public record describes a fix for a possible memory leak, but does not provide CVSS, CWE, impact details, or exploitation evidence.

Executive priority

Treat as a patch-tracking item, with higher priority for servers using ksmbd for SMB file sharing. Current public evidence does not justify emergency handling absent exposed ksmbd use or vendor escalation.

Technical view

The resolved kernel issue is in ksmbd smb2_lock(). The source states argv must be freed when setup_async_work fails or when the current process wakes up. Affected data points include Linux 5.15 through fixed stable versions including 5.15.145, 6.1.16, 6.2.3, and 6.3 context.

Likely exposure

Exposure appears limited to Linux systems using the in-kernel ksmbd SMB server on affected kernel versions. Systems not running ksmbd are less likely to be exposed, but the source bundle does not define exact runtime preconditions.

Exploitation context

No cited source reports active exploitation, and KEV status is false. The available sources describe a memory leak fix, not a public exploit path or confirmed attacker impact.

Researcher notes

The record is sparse: no CVSS vector, CWE, detailed affected matrix, or exploitability assessment is provided. Analysis should focus on kernel branch backports and whether smb2_lock() paths are reachable in local deployments.

Mitigation direction

  • Update affected Linux kernels through supported vendor or distribution channels.
  • Ensure the update includes the referenced stable ksmbd fixes.
  • Prioritize systems running ksmbd for SMB file sharing.
  • If updates are unavailable, check vendor guidance for supported workarounds.

Validation and detection

  • Inventory Linux hosts and kernel versions against vendor advisories.
  • Confirm whether ksmbd is enabled or loaded on each host.
  • Verify installed kernels include the stable fix commits or downstream backports.
  • Review SMB service exposure for systems awaiting update.
Prepared
Confidence
medium
Sources
6

Public sources used

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-54162 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9unaffected
LinuxLinux5.15, 0, 5.15.145, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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