From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89853: scsi: qla2xxx: Fix FCE trace use-after-free during firmware dump
Date: Wed, 16 Sep 2026 11:29:43 +0100 [thread overview]
Message-ID: <2026091617-CVE-2026-89853-e675@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Fix FCE trace use-after-free during firmware dump
qla2x00_free_fce_trace() freed and cleared ha->fce while holding only
fce_mutex. The firmware-dump consumers qla27xx_fwdt_entry_t264() and
qla25xx_copy_fce() read ha->fce (NULL check followed by a copy of the
buffer) under hardware_lock and never take fce_mutex. A debugfs FCE
disable could therefore free the DMA buffer between a dump's NULL check
and its copy, resulting in a use-after-free.
Unpublish ha->fce under hardware_lock, then release the lock and free
the DMA buffer (dma_free_coherent() may sleep). A concurrent dump either
completes its check and copy with the buffer still valid, or observes
ha->fce == NULL and skips it.
The Linux kernel CVE team has assigned CVE-2026-89853 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10.235 with commit 3a5a789494875376d1f8063ec5ecc6beafda2ce1 and fixed in 5.10.270 with commit 423487f03e325b8665d20a2a3171fe012b1a4fa9
Issue introduced in 5.15.179 with commit 73d3d3c66f108bc47922490f8500842530139975 and fixed in 5.15.221 with commit 7bd308cd893e8cce023d03a40a2f0adccaff0175
Issue introduced in 6.1.129 with commit 57c029cab0d908942e3ed9ff9fd0361144d01944 and fixed in 6.1.188 with commit edc464a4fc96e2720d166e7cc7e7a6827b086760
Issue introduced in 6.6.78 with commit 217230bc8796a922d5b15a9a94ec4414b2d2b3e3 and fixed in 6.6.157 with commit 6003e79148eca73d7cafb076f5be47e234d543d0
Issue introduced in 6.12.14 with commit 2cf3c3fe9a11aa168e80c966494c58548b9aed5d and fixed in 6.12.110 with commit ef9b89f6c92274c3670403fd06130ca25f685050
Issue introduced in 6.14 with commit 841df27d619ee1f5ca6473e15227b39d6136562d and fixed in 6.18.51 with commit 8e7a26931b6111583cfeaf49c068f26524dc3af2
Issue introduced in 6.14 with commit 841df27d619ee1f5ca6473e15227b39d6136562d and fixed in 7.2.5 with commit 41ef7edde27ac87d55ffc703da44e78aa8c2e896
Issue introduced in 6.14 with commit 841df27d619ee1f5ca6473e15227b39d6136562d and fixed in 7.3-rc1 with commit 53298efcbbb0f0438366d45cb7ed7e6d93dd5531
Issue introduced in 6.13.3 with commit a89872a61b914378591f16e428dd221c5e2059b2
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-89853
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_init.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/423487f03e325b8665d20a2a3171fe012b1a4fa9
https://git.kernel.org/stable/c/7bd308cd893e8cce023d03a40a2f0adccaff0175
https://git.kernel.org/stable/c/edc464a4fc96e2720d166e7cc7e7a6827b086760
https://git.kernel.org/stable/c/6003e79148eca73d7cafb076f5be47e234d543d0
https://git.kernel.org/stable/c/ef9b89f6c92274c3670403fd06130ca25f685050
https://git.kernel.org/stable/c/8e7a26931b6111583cfeaf49c068f26524dc3af2
https://git.kernel.org/stable/c/41ef7edde27ac87d55ffc703da44e78aa8c2e896
https://git.kernel.org/stable/c/53298efcbbb0f0438366d45cb7ed7e6d93dd5531
reply other threads:[~2026-09-16 10: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=2026091617-CVE-2026-89853-e675@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.