From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43473: scsi: mpi3mr: Add NULL checks when resetting request and reply queues
Date: Fri, 8 May 2026 16:23:22 +0200 [thread overview]
Message-ID: <2026050805-CVE-2026-43473-cae2@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: mpi3mr: Add NULL checks when resetting request and reply queues
The driver encountered a crash during resource cleanup when the reply and
request queues were NULL due to freed memory. This issue occurred when the
creation of reply or request queues failed, and the driver freed the memory
first, but attempted to mem set the content of the freed memory, leading to
a system crash.
Add NULL pointer checks for reply and request queues before accessing the
reply/request memory during cleanup
The Linux kernel CVE team has assigned CVE-2026-43473 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.203 with commit f8e833572a3e12a2a1ffe7b3646af024264d38ca
Fixed in 6.1.167 with commit 7df0296ad4e9253d12c6dbe7f120044dddc95600
Fixed in 6.6.130 with commit 7da755e0d02e9ca035065127e108d1fed8950dc8
Fixed in 6.12.78 with commit 78d3f201f8b609928eade53cf03a52df5415aaf7
Fixed in 6.18.19 with commit e978a36f332ede78eb4de037b517db16265d420d
Fixed in 6.19.9 with commit 220d7ca70611a73d50ef8e9edac630ed1ececb7c
Fixed in 7.0 with commit fa96392ebebc8fade2b878acb14cce0f71016503
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-2026-43473
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_fw.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/f8e833572a3e12a2a1ffe7b3646af024264d38ca
https://git.kernel.org/stable/c/7df0296ad4e9253d12c6dbe7f120044dddc95600
https://git.kernel.org/stable/c/7da755e0d02e9ca035065127e108d1fed8950dc8
https://git.kernel.org/stable/c/78d3f201f8b609928eade53cf03a52df5415aaf7
https://git.kernel.org/stable/c/e978a36f332ede78eb4de037b517db16265d420d
https://git.kernel.org/stable/c/220d7ca70611a73d50ef8e9edac630ed1ececb7c
https://git.kernel.org/stable/c/fa96392ebebc8fade2b878acb14cce0f71016503
reply other threads:[~2026-05-08 14:27 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=2026050805-CVE-2026-43473-cae2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox