Kernel memory corruption via oversized debugfs write
Published Dec 24, 2025 · Updated Dec 24, 2025
Stack-based buffer overflow in Linux lpfc debugfs allows local users to overwrite kernel memory through an oversized lockstat write. lpfc_debugfs_lockstat_write() passes an attacker-controlled byte count to copy_from_user() without limiting it to the fixed mybuf array. The local, low-privilege path requires a reachable lpfc debugfs entry, and successful corruption exposes kernel confidentiality, integrity, and availability.
Summary
What happened
Stack-based buffer overflow in Linux lpfc debugfs allows local users to overwrite kernel memory through an oversized lockstat write. lpfc_debugfs_lockstat_write() passes an attacker-controlled byte count to copy_from_user() without limiting it to the fixed mybuf array. The local, low-privilege path requires a reachable lpfc debugfs entry, and successful corruption exposes kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2023-54102
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <644a9d5e22761a41d5005a26996a643da96de962
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a9df88cb31dcbd72104ec5883f35cbc1fb587e47
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ad050f6cf681ebb850a9d4bc19474d3896476301
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c6087b82a9146826564a55c5ca0164cac40348f5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e0e7faee3a7dd6f51350cda64997116a247eb045
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f91037487036e2d2f18d3c2481be6b9a366bde7f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo