[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025032721-CVE-2023-52937-605d@gregkh>
Date: Thu, 27 Mar 2025 17:37:27 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2023-52937: HV: hv_balloon: fix memory leak with using debugfs_lookup()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HV: hv_balloon: 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-52937 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.0 with commit d180e0a1be6cea2b7436fadbd1c96aecdf3c46c7 and fixed in 6.1.11 with commit 0b570a059cf42ad6e2eb632f47c23813d58d8303
Issue introduced in 6.0 with commit d180e0a1be6cea2b7436fadbd1c96aecdf3c46c7 and fixed in 6.2 with commit 6dfb0771429a63db8561d44147f2bb76f93e1c86
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-52937
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/hv/hv_balloon.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/0b570a059cf42ad6e2eb632f47c23813d58d8303
https://git.kernel.org/stable/c/6dfb0771429a63db8561d44147f2bb76f93e1c86
Powered by blists - more mailing lists