From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-53371: net/mlx5e: fix memory leak in mlx5e_fs_tt_redirect_any_create
Date: Thu, 18 Sep 2025 15:34:16 +0200 [thread overview]
Message-ID: <2025091855-CVE-2023-53371-e5f9@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: fix memory leak in mlx5e_fs_tt_redirect_any_create
The memory pointed to by the fs->any pointer is not freed in the error
path of mlx5e_fs_tt_redirect_any_create, which can lead to a memory leak.
Fix by freeing the memory in the error path, thereby making the error path
identical to mlx5e_fs_tt_redirect_any_destroy().
The Linux kernel CVE team has assigned CVE-2023-53371 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit 0f575c20bf0686caf3d82d6c626c2e1e4a4c36e6 and fixed in 6.1.40 with commit 75df2fe6d160e16be880aacacd521b135d7177c9
Issue introduced in 5.13 with commit 0f575c20bf0686caf3d82d6c626c2e1e4a4c36e6 and fixed in 6.4.5 with commit 8a75a6f169c3df3a94802314aa61282772ac75b8
Issue introduced in 5.13 with commit 0f575c20bf0686caf3d82d6c626c2e1e4a4c36e6 and fixed in 6.5 with commit 3250affdc658557a41df9c5fb567723e421f8bf2
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-53371
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/net/ethernet/mellanox/mlx5/core/en/fs_tt_redirect.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/75df2fe6d160e16be880aacacd521b135d7177c9
https://git.kernel.org/stable/c/8a75a6f169c3df3a94802314aa61282772ac75b8
https://git.kernel.org/stable/c/3250affdc658557a41df9c5fb567723e421f8bf2
reply other threads:[~2025-09-18 13:35 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=2025091855-CVE-2023-53371-e5f9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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.