[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091721-CVE-2023-53355-823c@gregkh>
Date: Wed, 17 Sep 2025 16:56:54 +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-53355: staging: pi433: 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:
staging: pi433: 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. This requires saving off the root directory dentry to make
creation of individual device subdirectories easier.
The Linux kernel CVE team has assigned CVE-2023-53355 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.18 with commit 04f3cda40e9f6653ae15ed3fcf26ef2860f4df66
Fixed in 6.2.5 with commit bb16f3102607b69e1a0233f4b73c6e337f86ef8d
Fixed in 6.3 with commit 2f36e789e540df6a9fbf471b3a2ba62a8b361586
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-53355
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/staging/pi433/pi433_if.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/04f3cda40e9f6653ae15ed3fcf26ef2860f4df66
https://git.kernel.org/stable/c/bb16f3102607b69e1a0233f4b73c6e337f86ef8d
https://git.kernel.org/stable/c/2f36e789e540df6a9fbf471b3a2ba62a8b361586
Powered by blists - more mailing lists