linux-cve-announce - CVE-2023-53408: trace/blktrace: fix memory leak with using debugfs

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: <2025091801-CVE-2023-53408-5a18@gregkh>
Date: Thu, 18 Sep 2025 15:59:05 +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-53408: trace/blktrace: 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:

trace/blktrace: 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-53408 to this issue.


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

	Fixed in 5.15.99 with commit a2e4b48d6f9b39aa19bafe223f9dd436a692fc80
	Fixed in 6.1.16 with commit 3036f5f5ae5210797d95446795df01c1249af9ad
	Fixed in 6.2.3 with commit 5286b72fb425291af5f4ca7285d73c16a08d8691
	Fixed in 6.3 with commit 83e8864fee26f63a7435e941b7c36a20fd6fe93e

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-53408
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:
	kernel/trace/blktrace.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/a2e4b48d6f9b39aa19bafe223f9dd436a692fc80
	https://git.kernel.org/stable/c/3036f5f5ae5210797d95446795df01c1249af9ad
	https://git.kernel.org/stable/c/5286b72fb425291af5f4ca7285d73c16a08d8691
	https://git.kernel.org/stable/c/83e8864fee26f63a7435e941b7c36a20fd6fe93e