[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091802-CVE-2023-53415-ea27@gregkh>
Date: Thu, 18 Sep 2025 15:59:12 +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-53415: USB: dwc3: 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:
USB: dwc3: 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.
Note, the root dentry for the debugfs directory for the device needs to
be saved so we don't have to keep looking it up, which required a bit
more refactoring to properly create and remove it when needed.
The Linux kernel CVE team has assigned CVE-2023-53415 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.100 with commit cf52c320cf74245ce1c12b0bd48f77b87d77fbc9
Fixed in 6.1.18 with commit ce234af49d103d95e3fdca59b25e0d0242f41bb4
Fixed in 6.2.5 with commit bab872b638130a18fd54d9adfad7db77ed6457be
Fixed in 6.3 with commit be308d68785b205e483b3a0c61ba3a82da468f2c
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-53415
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/usb/dwc3/core.h
drivers/usb/dwc3/debug.h
drivers/usb/dwc3/debugfs.c
drivers/usb/dwc3/gadget.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/cf52c320cf74245ce1c12b0bd48f77b87d77fbc9
https://git.kernel.org/stable/c/ce234af49d103d95e3fdca59b25e0d0242f41bb4
https://git.kernel.org/stable/c/bab872b638130a18fd54d9adfad7db77ed6457be
https://git.kernel.org/stable/c/be308d68785b205e483b3a0c61ba3a82da468f2c
Powered by blists - more mailing lists