From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2023-52702: net: openvswitch: fix possible memory leak in ovs_meter_cmd_set()
Date: Tue, 21 May 2024 17:23:00 +0200 [thread overview]
Message-ID: <2024052156-CVE-2023-52702-ebca@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: openvswitch: fix possible memory leak in ovs_meter_cmd_set()
old_meter needs to be free after it is detached regardless of whether
the new meter is successfully attached.
The Linux kernel CVE team has assigned CVE-2023-52702 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.8 with commit c7c4c44c9a95 and fixed in 5.10.169 with commit c0f65ee0a332
Issue introduced in 5.8 with commit c7c4c44c9a95 and fixed in 5.15.95 with commit 1563e998a938
Issue introduced in 5.8 with commit c7c4c44c9a95 and fixed in 6.1.13 with commit e336a9e08618
Issue introduced in 5.8 with commit c7c4c44c9a95 and fixed in 6.2 with commit 2fa28f5c6fcb
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-52702
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:
net/openvswitch/meter.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/c0f65ee0a3329eb4b94beaef0268633696e2d0c6
https://git.kernel.org/stable/c/1563e998a938f095548054ef09e277b562b79536
https://git.kernel.org/stable/c/e336a9e08618203a456fb5367f1387b14554f55e
https://git.kernel.org/stable/c/2fa28f5c6fcbfc794340684f36d2581b4f2d20b5
reply other threads:[~2024-05-21 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024052156-CVE-2023-52702-ebca@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.