CVE Intelligence
Unknown

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

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.

Published Sep 16, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.21%
ahead of 11% of scored CVEs · Oct 19, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ 3a5a789494875376d1f8063ec5ecc6beafda2ce1 and < 423487f03e325b8665d20a2a3171fe012b1a4fa9≥ 73d3d3c66f108bc47922490f8500842530139975 and < 7bd308cd893e8cce023d03a40a2f0adccaff0175≥ 57c029cab0d908942e3ed9ff9fd0361144d01944 and < edc464a4fc96e2720d166e7cc7e7a6827b086760≥ 217230bc8796a922d5b15a9a94ec4414b2d2b3e3 and < 6003e79148eca73d7cafb076f5be47e234d543d0≥ 2cf3c3fe9a11aa168e80c966494c58548b9aed5d and < ef9b89f6c92274c3670403fd06130ca25f685050≥ 841df27d619ee1f5ca6473e15227b39d6136562d and < 8e7a26931b6111583cfeaf49c068f26524dc3af2≥ 841df27d619ee1f5ca6473e15227b39d6136562d and < 41ef7edde27ac87d55ffc703da44e78aa8c2e896≥ 841df27d619ee1f5ca6473e15227b39d6136562d and < 53298efcbbb0f0438366d45cb7ed7e6d93dd5531
and 8 more version a89872a61b914378591f16e428dd221c5e2059b2≥ 5.10.235 and < 5.10.270≥ 5.15.179 and < 5.15.221≥ 6.1.129 and < 6.1.188≥ 6.6.78 and < 6.6.157≥ 6.12.14 and < 6.12.110≥ 6.13.3 and < 6.14version 6.14
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 19, 2026 · 4 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Sep 16, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

10 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 2d
  • CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 2d
  • CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 2d
  • CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 2d
  • CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 2d
  • CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-89853 is "scsi: qla2xxx: Fix FCE trace use-after-free during firmware dump", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.