linux-cve-announce - CVE-2023-54115: pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025122414-CVE-2023-54115-19b7@gregkh>
Date: Wed, 24 Dec 2025 14:07:12 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54115: pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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).

The Linux kernel CVE team has assigned CVE-2023-54115 to this issue.


Affected and fixed versions
===========================

	Fixed in 4.14.324 with commit bde0b6da7bd893c37afaee3555cc3ac3be582313
	Fixed in 4.19.293 with commit 2d45e2be0be35a3d66863563ed2591ee18a6897e
	Fixed in 5.4.255 with commit 22100df1d57f04cf2370d5347b9ef547f481deea
	Fixed in 5.10.192 with commit 04bb8af40a7729c398ed4caea7e66cedd2881719
	Fixed in 5.15.128 with commit 97fd1c8e9c5aa833aab7e836760bc13103afa892
	Fixed in 6.1.47 with commit e8a80cf06b4bb0396212289d651b384c949f09d0
	Fixed in 6.4.12 with commit fd53a1f28faba2c4806c055e706a7721006291c1
	Fixed in 6.5 with commit c85fd9422fe0f5d667305efb27f56d09eab120b0

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-54115
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/pcmcia/rsrc_nonstatic.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/bde0b6da7bd893c37afaee3555cc3ac3be582313
	https://git.kernel.org/stable/c/2d45e2be0be35a3d66863563ed2591ee18a6897e
	https://git.kernel.org/stable/c/22100df1d57f04cf2370d5347b9ef547f481deea
	https://git.kernel.org/stable/c/04bb8af40a7729c398ed4caea7e66cedd2881719
	https://git.kernel.org/stable/c/97fd1c8e9c5aa833aab7e836760bc13103afa892
	https://git.kernel.org/stable/c/e8a80cf06b4bb0396212289d651b384c949f09d0
	https://git.kernel.org/stable/c/fd53a1f28faba2c4806c055e706a7721006291c1
	https://git.kernel.org/stable/c/c85fd9422fe0f5d667305efb27f56d09eab120b0