[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091802-CVE-2023-53411-530b@gregkh>
Date: Thu, 18 Sep 2025 15:59:08 +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-53411: PM: EM: 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:
PM: EM: 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-53411 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.173 with commit e974e8f1e37d22c0de07374f8ddc84073fef2f1d
Fixed in 5.15.99 with commit 84e4d4885d0ae011860fb599d50d01b8fdca2b87
Fixed in 6.1.16 with commit 5100c4efc30636aa48ac517dece3c3b7f84fe367
Fixed in 6.2.3 with commit 30fee10192e1239478a0987bc7ee445d5e980d46
Fixed in 6.3 with commit a0e8c13ccd6a9a636d27353da62c2410c4eca337
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-53411
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/power/energy_model.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/e974e8f1e37d22c0de07374f8ddc84073fef2f1d
https://git.kernel.org/stable/c/84e4d4885d0ae011860fb599d50d01b8fdca2b87
https://git.kernel.org/stable/c/5100c4efc30636aa48ac517dece3c3b7f84fe367
https://git.kernel.org/stable/c/30fee10192e1239478a0987bc7ee445d5e980d46
https://git.kernel.org/stable/c/a0e8c13ccd6a9a636d27353da62c2410c4eca337
Powered by blists - more mailing lists