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
| ||
|
Message-ID: <2025050222-CVE-2023-53097-fd46@gregkh> Date: Fri, 2 May 2025 17:56:02 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53097: powerpc/iommu: fix memory leak with using debugfs_lookup() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. The Linux kernel CVE team has assigned CVE-2023-53097 to this issue. Affected and fixed versions =========================== Fixed in 5.15.103 with commit e3a62a35f903fd8be5b44542fe3901ec45f16757 Fixed in 6.1.20 with commit 24c1bd1cd0d1ff821fd7d2f01a1e648c7882dfc2 Fixed in 6.2.7 with commit 4050498c0ae3946c223fc63e9dd7b878b76611e0 Fixed in 6.3 with commit b505063910c134778202dfad9332dfcecb76bab3 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-53097 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: arch/powerpc/kernel/iommu.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/e3a62a35f903fd8be5b44542fe3901ec45f16757 https://git.kernel.org/stable/c/24c1bd1cd0d1ff821fd7d2f01a1e648c7882dfc2 https://git.kernel.org/stable/c/4050498c0ae3946c223fc63e9dd7b878b76611e0 https://git.kernel.org/stable/c/b505063910c134778202dfad9332dfcecb76bab3
Powered by blists - more mailing lists