CVE-2023-54102: scsi: lpfc: Prevent lpfc_debugfs_lockstat_write() buffer overflow
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Fixed version: Linux Linux 644a9d5e22761a41d5005a26996a643da96de962, a9df88cb31dcbd72104ec5883f35cbc1fb587e47, ad050f6cf681ebb850a9d4bc19474d3896476301.
Low priority for now. Upgrade to Linux Linux 644a9d5e22761a41d5005a26996a643da96de962, a9df88cb31dcbd72104ec5883f35cbc1fb587e47, ad050f6cf681ebb850a9d4bc19474d3896476301 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.1affected
- 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e and later · before 644a9d5e22761a41d5005a26996a643da96de962affected · git
- 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e and later · before e0e7faee3a7dd6f51350cda64997116a247eb045affected · git
- 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e and later · before f91037487036e2d2f18d3c2481be6b9a366bde7faffected · git
- 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e and later · before a9df88cb31dcbd72104ec5883f35cbc1fb587e47affected · git
- 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e and later · before ad050f6cf681ebb850a9d4bc19474d3896476301affected · git
- 6a828b0f6192b4930894925d1c1d0dc1f1d99e6e and later · before c6087b82a9146826564a55c5ca0164cac40348f5affected · git
- before 5.1not affected · semver
- 5.4.244 and later · up to and including 5.4.*not affected · semver
- 5.10.181 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54100Dec 24, 2025 · scsi: qedi: Fix use after free bug in qedi_remove()31Monitor
- ← EarlierCVE-2023-54101Dec 24, 2025 · driver: soc: xilinx: use _safe loop iterator to avoid a use after free0Monitor
- Later →CVE-2023-54104Dec 24, 2025 · mtd: rawnand: fsl_upm: Fix an off-by one test in fun_exec_op()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 644a9d5e22761a41d5005a26996a643da96de962 | Vendor (CNA) |
| Linux Linux | a9df88cb31dcbd72104ec5883f35cbc1fb587e47 | Vendor (CNA) |
| Linux Linux | ad050f6cf681ebb850a9d4bc19474d3896476301 | Vendor (CNA) |
| Linux Linux | c6087b82a9146826564a55c5ca0164cac40348f5 | Vendor (CNA) |
| Linux Linux | e0e7faee3a7dd6f51350cda64997116a247eb045 | Vendor (CNA) |
| Linux Linux | f91037487036e2d2f18d3c2481be6b9a366bde7f | Vendor (CNA) |
| debian:linux | 6.1.37-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/a9df88cb31dcbd72104ec5883f35cbc1fb587e47
- git.kernel.org/stable/c/ad050f6cf681ebb850a9d4bc19474d3896476301
- git.kernel.org/stable/c/c6087b82a9146826564a55c5ca0164cac40348f5
- git.kernel.org/stable/c/e0e7faee3a7dd6f51350cda64997116a247eb045
- git.kernel.org/stable/c/f91037487036e2d2f18d3c2481be6b9a366bde7f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.