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

> A use-after-free in the qla2xxx SCSI driver allows local attackers with high privileges to execute arbitrary code or escalate privileges during firmware dumps.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101142, BELL-CVE-2026-89853, DEBIAN-CVE-2026-89853, GHSA-3hhp-7j3w-92c8, UBUNTU-CVE-2026-89853

## What is CVE-2026-89853?

CVE-2026-89853 is an use after free vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-89853?


## How do I fix CVE-2026-89853?

Apply the vendor's patch.

## Is CVE-2026-89853 being exploited?

There is no known exploitation of CVE-2026-89853 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89853 and fix it if it is affected.

What it is: CVE-2026-89853 is an use after free vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89853 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89853/ (Markdown: https://insights.sbomify.com/CVE-2026-89853/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89853
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89853
- OSV: https://osv.dev/vulnerability/CVE-2026-89853

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89853/
Summaries are generated and may contain mistakes; the official description above is the record.