From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-53127: scsi: mpi3mr: Fix expander node leak in mpi3mr_remove()
Date: Fri, 2 May 2025 17:56:32 +0200 [thread overview]
Message-ID: <2025050233-CVE-2023-53127-a596@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: mpi3mr: Fix expander node leak in mpi3mr_remove()
Add a missing resource clean up in .remove.
The Linux kernel CVE team has assigned CVE-2023-53127 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit e22bae30667a7e74ed057e00fb6e8c79e0738de3 and fixed in 6.1.21 with commit 0023972a7593720f8878aed06c03ac9e541078be
Issue introduced in 6.1 with commit e22bae30667a7e74ed057e00fb6e8c79e0738de3 and fixed in 6.2.8 with commit cf9777be5683c5e55680c089df02ee27d2226aa8
Issue introduced in 6.1 with commit e22bae30667a7e74ed057e00fb6e8c79e0738de3 and fixed in 6.3 with commit ce756daa36e1ba271bb3334267295e447aa57a5c
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-53127
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/scsi/mpi3mr/mpi3mr.h
drivers/scsi/mpi3mr/mpi3mr_os.c
drivers/scsi/mpi3mr/mpi3mr_transport.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/0023972a7593720f8878aed06c03ac9e541078be
https://git.kernel.org/stable/c/cf9777be5683c5e55680c089df02ee27d2226aa8
https://git.kernel.org/stable/c/ce756daa36e1ba271bb3334267295e447aa57a5c
reply other threads:[~2025-05-02 16:00 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=2025050233-CVE-2023-53127-a596@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.