LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54260: cifs: Fix lost destroy smbd connection when MR allocate failed

In the Linux kernel, the following vulnerability has been resolved: cifs: Fix lost destroy smbd connection when MR allocate failed If the MR allocate failed, the smb direct connection info is NULL, then smbd_destroy() will directly return, then the connection info will be leaked. Let's set the smb direct connection info to the server before call smbd_destroy().

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a cleanup bug in the CIFS/SMB Direct code path. If memory-region allocation fails, connection cleanup can return early and leak connection information. The business risk appears limited from the provided evidence, but affected systems should take normal kernel maintenance updates, especially where CIFS over SMB Direct/RDMA is used.

Executive priority

Treat as routine kernel hygiene unless your environment depends heavily on CIFS over SMB Direct/RDMA. There is no supplied evidence of active exploitation or high-impact compromise, but unpatched kernel resource leaks can affect service stability over time.

Technical view

The CVE describes a resource leak in Linux kernel CIFS SMB Direct handling. On MR allocation failure, smb direct connection info may be NULL, causing smbd_destroy() to return without freeing connection info. The fix sets the connection info on the server before calling smbd_destroy().

Likely exposure

Exposure is most likely on Linux systems using CIFS with SMB Direct/RDMA on kernel versions covered by the CVE record. Systems not using CIFS or SMB Direct appear less likely to hit the affected path, based only on the supplied sources.

Exploitation context

The source bundle marks KEV as false and provides no public exploitation evidence. The issue appears tied to an allocation-failure cleanup path, suggesting reliability or resource-exhaustion concern rather than confirmed code execution. Practical exploitability is not established by the supplied evidence.

Researcher notes

The record lacks CVSS, CWE, and detailed attack prerequisites. Analysis should focus on the CIFS SMB Direct MR allocation failure path and whether repeated failure conditions can accumulate leaked connection state in realistic deployments.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check distribution advisories for backported fixes matching your running kernel.
  • Prioritize systems using CIFS mounts with SMB Direct or RDMA support.
  • Track this through normal kernel vulnerability management until patched.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify hosts using CIFS mounts and SMB Direct/RDMA features.
  • Confirm the running kernel includes a vendor backport of the stable fix.
  • Review distro security notes for CVE-2023-54260 remediation status.
Prepared
Confidence
medium
Sources
9

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-54260 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
8Source 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
LinuxLinuxc7398583340a6d82b8bb7f7f21edcde27dc6a898, c7398583340a6d82b8bb7f7f21edcde27dc6a898, c7398583340a6d82b8bb7f7f21edcde27dc6a898, c7398583340a6d82b8bb7f7f21edcde27dc6a898, c7398583340a6d82b8bb7f7f21edcde27dc6a898, c7398583340a6d82b8bb7f7f21edcde27dc6a898, c7398583340a6d82b8bb7f7f21edcde27dc6a898unaffected
LinuxLinux4.16, 0, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 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.