# CVE-2026-89851: scsi: qla2xxx: Fix FCE trace enable parsing in debugfs

> A local attacker with debugfs access can trigger a kernel null pointer dereference in the qla2xxx driver, causing a system crash.

- **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-101399, BELL-CVE-2026-89851, DEBIAN-CVE-2026-89851, GHSA-hwqc-mqvr-m7jg, UBUNTU-CVE-2026-89851

## What is CVE-2026-89851?

CVE-2026-89851 is a 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 enable parsing in debugfs

qla2x00_dfs_fce_write() called kstrtoul() with a NULL result pointer,
so a successful parse would dereference NULL and oops. Worse, the int
return value (0 on success, negative errno on failure) was assigned to
the unsigned long enable flag, inverting the intended logic: a valid
number was treated as "disable" while a parse failure enabled FCE.

Parse the value into enable and propagate parse errors to userspace.

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


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

Apply the vendor's patch.

## Is CVE-2026-89851 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89851 is a 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-89851 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-89851/ (Markdown: https://insights.sbomify.com/CVE-2026-89851/index.md)
```

## Sources

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

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