From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43414: scsi: qla2xxx: Completely fix fcport double free
Date: Fri, 8 May 2026 16:22:23 +0200 [thread overview]
Message-ID: <2026050844-CVE-2026-43414-2950@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Completely fix fcport double free
In qla24xx_els_dcmd_iocb() sp->free is set to qla2x00_els_dcmd_sp_free().
When an error happens, this function is called by qla2x00_sp_release(),
when kref_put() releases the first and the last reference.
qla2x00_els_dcmd_sp_free() frees fcport by calling qla2x00_free_fcport().
Doing it one more time after kref_put() is a bad idea.
The Linux kernel CVE team has assigned CVE-2026-43414 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 4895009c4bb72f71f2e682f1e7d2c2d96e482087 and fixed in 6.19.9 with commit d48ea85463f5b34f7b92ea0a13eddf1ab993da7b
Issue introduced in 6.9 with commit 4895009c4bb72f71f2e682f1e7d2c2d96e482087 and fixed in 7.0 with commit c0b7da13a04bd70ef6070bfb9ea85f582294560a
Issue introduced in 5.15.154 with commit 7861213201838480dc222634c56fb6db113d010d
Issue introduced in 6.1.84 with commit 3b9d72442adfbc9ddb0f76dd1b03977b3a578b16
Issue introduced in 6.6.24 with commit ef23850940d9a52c39936d27254824ccf5e9b6bd
Issue introduced in 6.7.12 with commit 6c6bf6cacf9461f8d301cfac4f9c175d80cbcc63
Issue introduced in 6.8.3 with commit cd10dee1f07a782f5aa05703c55299ca86a85ee4
Issue introduced in 5.15.154 with commit b03e626bd6d3f0684f56ee1890d70fc9ca991c04
Issue introduced in 6.1.84 with commit 282877633b25d67021a34169c5b5519b1d4ef65e
Issue introduced in 6.6.24 with commit f85af9f1aa5e2f53694a6cbe72010f754b5ff862
Issue introduced in 6.7.12 with commit 9b43d2884b54d415caab48878b526dfe2ae9921b
Issue introduced in 6.8.3 with commit 846fb9f112f618ec6ae181d8dae7961652574774
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-43414
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/d48ea85463f5b34f7b92ea0a13eddf1ab993da7b
https://git.kernel.org/stable/c/c0b7da13a04bd70ef6070bfb9ea85f582294560a
reply other threads:[~2026-05-08 14:24 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=2026050844-CVE-2026-43414-2950@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