Kernel memory leak via unreleased PCMCIA socket data
Published Dec 24, 2025 · Updated Dec 24, 2025
A memory leak in affected Linux kernel branches allows attackers to retain kernel memory when PCMCIA socket resources are released. The nonstatic_release_resource_db() cleanup path frees a socket's resources but omits freeing its socket_data allocation, leaving a 64-byte object unreferenced. The reported reproduction used manual yenta_cardbus binding and unbinding on PCMCIA-capable hardware; the record reports no crash or other impact.
Summary
What happened
A memory leak in affected Linux kernel branches allows attackers to retain kernel memory when PCMCIA socket resources are released. The nonstatic_release_resource_db() cleanup path frees a socket's resources but omits freeing its socket_data allocation, leaving a 64-byte object unreferenced. The reported reproduction used manual yenta_cardbus binding and unbinding on PCMCIA-capable hardware; the record reports no crash or other impact.
The record
- CVE
- CVE-2023-54115
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
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 <04bb8af40a7729c398ed4caea7e66cedd2881719
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <22100df1d57f04cf2370d5347b9ef547f481deea
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2d45e2be0be35a3d66863563ed2591ee18a6897e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <97fd1c8e9c5aa833aab7e836760bc13103afa892
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bde0b6da7bd893c37afaee3555cc3ac3be582313
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c85fd9422fe0f5d667305efb27f56d09eab120b0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e8a80cf06b4bb0396212289d651b384c949f09d0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd53a1f28faba2c4806c055e706a7721006291c1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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