From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-53451: scsi: qla2xxx: Fix potential NULL pointer dereference
Date: Wed, 1 Oct 2025 13:42:21 +0200 [thread overview]
Message-ID: <2025100103-CVE-2023-53451-bb02@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Fix potential NULL pointer dereference
Klocwork tool reported 'cur_dsd' may be dereferenced. Add fix to validate
pointer before dereferencing the pointer.
The Linux kernel CVE team has assigned CVE-2023-53451 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.322 with commit 02405f4023866ae91a611b5b85cb2e074ec2de5a
Fixed in 4.19.291 with commit ee4c9a93238b9ce3703942500cb1aeacf77090d2
Fixed in 5.4.251 with commit 4f90a8b0481615622bd0558aa8cf361bea872045
Fixed in 5.10.188 with commit 2bea9c1c983152c5411f5a2f1113cb790ce1389d
Fixed in 5.15.121 with commit 5a52a2e14fe866541bbc0033058e44bf0bf0c580
Fixed in 6.1.40 with commit ce2cdbe530b0066bae1f98dbab590a232d507eaa
Fixed in 6.4.5 with commit af7affc0f6b82a5bde430fc4f0dcf70963442fbc
Fixed in 6.5 with commit 464ea494a40c6e3e0e8f91dd325408aaf21515ba
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-53451
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/qla2xxx/qla_iocb.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/02405f4023866ae91a611b5b85cb2e074ec2de5a
https://git.kernel.org/stable/c/ee4c9a93238b9ce3703942500cb1aeacf77090d2
https://git.kernel.org/stable/c/4f90a8b0481615622bd0558aa8cf361bea872045
https://git.kernel.org/stable/c/2bea9c1c983152c5411f5a2f1113cb790ce1389d
https://git.kernel.org/stable/c/5a52a2e14fe866541bbc0033058e44bf0bf0c580
https://git.kernel.org/stable/c/ce2cdbe530b0066bae1f98dbab590a232d507eaa
https://git.kernel.org/stable/c/af7affc0f6b82a5bde430fc4f0dcf70963442fbc
https://git.kernel.org/stable/c/464ea494a40c6e3e0e8f91dd325408aaf21515ba
reply other threads:[~2025-10-01 11:54 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=2025100103-CVE-2023-53451-bb02@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.