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

> A local attacker with debugfs access can trigger a buffer overflow in the lpfc SCSI driver, potentially leading to privilege escalation or system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54102, DEBIAN-CVE-2023-54102, GHSA-hpjg-jc89-xqgf, UBUNTU-CVE-2023-54102

## What is CVE-2023-54102?

CVE-2023-54102 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2023-54102?


## How do I fix CVE-2023-54102?

Apply the vendor's patch.

## Is CVE-2023-54102 being exploited?

There is no known exploitation of CVE-2023-54102 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54102 and fix it if it is affected.

What it is: CVE-2023-54102 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54102 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-54102/ (Markdown: https://insights.sbomify.com/CVE-2023-54102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-54102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-54102
- OSV: https://osv.dev/vulnerability/CVE-2023-54102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-54102/
Summaries are generated and may contain mistakes; the official description above is the record.