LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54102: scsi: lpfc: Prevent lpfc_debugfs_lockstat_write() buffer overflow

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Prevent lpfc_debugfs_lockstat_write() buffer overflow A static code analysis tool flagged the possibility of buffer overflow when using copy_from_user() for a debugfs entry. Currently, it is possible that copy_from_user() copies more bytes than what would fit in the mybuf char array. Add a min() restriction check between sizeof(mybuf) - 1 and nbytes passed from the userspace buffer to protect against buffer overflow.

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-54102 is a Linux kernel buffer-overflow issue in an lpfc debugfs write path. A userspace write could be copied into a fixed-size kernel buffer without the needed length cap. The public record provides fixes but no CVSS score, exploit report, or business-impact evidence.

Executive priority

Prioritize as an exposure-confirmation and routine kernel-update item. Escalate if business-critical storage hosts run affected kernels with lpfc enabled, because kernel memory corruption issues can carry outsized operational risk even when public severity data is incomplete.

Technical view

The vulnerable function is lpfc_debugfs_lockstat_write(). The issue is an unchecked copy_from_user() length where nbytes could exceed mybuf capacity. The fix adds a min() restriction against sizeof(mybuf) - 1 before copying, preventing overflow of the local char array.

Likely exposure

Exposure appears limited to affected Linux kernel versions using the lpfc SCSI driver and the relevant debugfs entry. The source lists Linux affected entries including 5.1, 5.4.244, 5.10.181, 5.15.113, 6.1.30, 6.3.4, and 6.4.

Exploitation context

The source bundle does not show active exploitation, public exploit code, KEV listing, or detailed exploit prerequisites. Treat this as a kernel hardening and patch-management issue unless local evidence shows the lpfc debugfs path is reachable in production.

Researcher notes

The record attributes discovery to static analysis and describes a bounded copy fix. Missing data includes CVSS, CWE, privileges required, whether debugfs must be mounted, and impact beyond overflow prevention. Avoid asserting exploitability without deeper kernel and configuration review.

Mitigation direction

  • Update to a kernel containing the referenced upstream stable fixes.
  • Apply distribution vendor kernel updates when available.
  • Prioritize systems using lpfc Fibre Channel storage adapters.
  • Check vendor guidance before applying operational workarounds.
  • Track this until asset inventory confirms exposure or remediation.

Validation and detection

  • Identify running kernel versions on Linux assets.
  • Check whether the lpfc driver is present or loaded.
  • Confirm the fixed kernel package or stable commit is installed.
  • Review vendor advisories for affected distribution-specific builds.
  • Record systems where debugfs exposure is operationally required.
Prepared
Confidence
medium
Sources
8

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-54102 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
7Source 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
LinuxLinux6a828b0f6192b4930894925d1c1d0dc1f1d99e6e, 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e, 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e, 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e, 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e, 6a828b0f6192b4930894925d1c1d0dc1f1d99e6eunaffected
LinuxLinux5.1, 0, 5.4.244, 5.10.181, 5.15.113, 6.1.30, 6.3.4, 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.