CVE-2026-89853

scsi: qla2xxx: Fix FCE trace use-after-free during firmware dump

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

217230bc8796a922d5b15a9a94ec4414b2d2b3e32cf3c3fe9a11aa168e80c966494c58548b9aed5d3a5a789494875376d1f8063ec5ecc6beafda2ce15.10.2355.15.17957c029cab0d908942e3ed9ff9fd0361144d019446.1.1296.12.146.13.36.146.6.7873d3d3c66f108bc47922490f8500842530139975841df27d619ee1f5ca6473e15227b39d6136562da89872a61b914378591f16e428dd221c5e2059b2
Vendor states this is fixed in 41ef7edde27ac87d55ffc703da44e78aa8c2e896 (fixed)
Vendor states this is fixed in 423487f03e325b8665d20a2a3171fe012b1a4fa9 (fixed)
Vendor states this is fixed in 53298efcbbb0f0438366d45cb7ed7e6d93dd5531 (fixed)
Vendor states this is fixed in 6003e79148eca73d7cafb076f5be47e234d543d0 (fixed)
Vendor states this is fixed in 7bd308cd893e8cce023d03a40a2f0adccaff0175 (fixed)
Vendor states this is fixed in 8e7a26931b6111583cfeaf49c068f26524dc3af2 (fixed)
Vendor states this is fixed in edc464a4fc96e2720d166e7cc7e7a6827b086760 (fixed)
Vendor states this is fixed in ef9b89f6c92274c3670403fd06130ca25f685050 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.14 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card