CVE-2023-54115: pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db()
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 04bb8af40a7729c398ed4caea7e66cedd2881719, 22100df1d57f04cf2370d5347b9ef547f481deea, 2d45e2be0be35a3d66863563ed2591ee18a6897e.
Low priority for now. Upgrade to Linux Linux 04bb8af40a7729c398ed4caea7e66cedd2881719, 22100df1d57f04cf2370d5347b9ef547f481deea, 2d45e2be0be35a3d66863563ed2591ee18a6897e 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: pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db() When nonstatic_release_resource_db() frees all resources associated with an PCMCIA socket, it forgets to free socket_data too, causing a memory leak observable with kmemleak: unreferenced object 0xc28d1000 (size 64): comm "systemd-udevd", pid 297, jiffies 4294898478 (age 194.484s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 f0 85 0e c3 00 00 00 00 ................ 00 00 00 00 0c 10 8d c2 00 00 00 00 00 00 00 00 ................ backtrace: [<ffda4245>] __kmem_cache_alloc_node+0x2d7/0x4a0 [<7e51f0c8>] kmalloc_trace+0x31/0xa4 [<d52b4ca0>] nonstatic_init+0x24/0x1a4 [pcmcia_rsrc] [<a2f13e08>] pcmcia_register_socket+0x200/0x35c [pcmcia_core] [<a728be1b>] yenta_probe+0x4d8/0xa70 [yenta_socket] [<c48fac39>] pci_device_probe+0x99/0x194 [<84b7c690>] really_probe+0x181/0x45c [<8060fe6e>] __driver_probe_device+0x75/0x1f4 [<b9b76f43>] driver_probe_device+0x28/0xac [<648b766f>] __driver_attach+0xeb/0x1e4 [<6e9659eb>] bus_for_each_dev+0x61/0xb4 [<25a669f3>] driver_attach+0x1e/0x28 [<d8671d6b>] bus_add_driver+0x102/0x20c [<df0d323c>] driver_register+0x5b/0x120 [<942cd8a4>] __pci_register_driver+0x44/0x4c [<e536027e>] __UNIQUE_ID___addressable_cleanup_module188+0x1c/0xfffff000 [iTCO_vendor_support] Fix this by freeing socket_data too. Tested on a Acer Travelmate 4002WLMi by manually binding/unbinding the yenta_cardbus driver (yenta_socket).
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th 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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before bde0b6da7bd893c37afaee3555cc3ac3be582313affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2d45e2be0be35a3d66863563ed2591ee18a6897eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 22100df1d57f04cf2370d5347b9ef547f481deeaaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 04bb8af40a7729c398ed4caea7e66cedd2881719affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 97fd1c8e9c5aa833aab7e836760bc13103afa892affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e8a80cf06b4bb0396212289d651b384c949f09d0affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fd53a1f28faba2c4806c055e706a7721006291c1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c85fd9422fe0f5d667305efb27f56d09eab120b0affected · git
- before 2.6.12not 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.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.13-1 | 6.4.13-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-54113Dec 24, 2025 · rcu: dump vmalloc memory info safely0Monitor
- ← EarlierCVE-2023-54114Dec 24, 2025 · net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment()0Monitor
- Later →CVE-2023-54117Dec 24, 2025 · s390/dcssblk: fix kernel crash with list_add corruption0Monitor
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 | 04bb8af40a7729c398ed4caea7e66cedd2881719 | Vendor (CNA) |
| Linux Linux | 22100df1d57f04cf2370d5347b9ef547f481deea | Vendor (CNA) |
| Linux Linux | 2d45e2be0be35a3d66863563ed2591ee18a6897e | Vendor (CNA) |
| Linux Linux | 97fd1c8e9c5aa833aab7e836760bc13103afa892 | Vendor (CNA) |
| Linux Linux | bde0b6da7bd893c37afaee3555cc3ac3be582313 | Vendor (CNA) |
| Linux Linux | c85fd9422fe0f5d667305efb27f56d09eab120b0 | Vendor (CNA) |
| Linux Linux | e8a80cf06b4bb0396212289d651b384c949f09d0 | Vendor (CNA) |
| Linux Linux | fd53a1f28faba2c4806c055e706a7721006291c1 | Vendor (CNA) |
| debian:linux | 6.1.52-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 (7 more)Show less
- git.kernel.org/stable/c/22100df1d57f04cf2370d5347b9ef547f481deea
- git.kernel.org/stable/c/2d45e2be0be35a3d66863563ed2591ee18a6897e
- git.kernel.org/stable/c/97fd1c8e9c5aa833aab7e836760bc13103afa892
- git.kernel.org/stable/c/bde0b6da7bd893c37afaee3555cc3ac3be582313
- git.kernel.org/stable/c/c85fd9422fe0f5d667305efb27f56d09eab120b0
- git.kernel.org/stable/c/e8a80cf06b4bb0396212289d651b384c949f09d0
- git.kernel.org/stable/c/fd53a1f28faba2c4806c055e706a7721006291c1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.