# CVE-2026-89863: scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check

> A NULL pointer dereference in the qla2xxx EDIF driver allows a local attacker to crash the Linux kernel via a crafted SCSI command completion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101457, BELL-CVE-2026-89863, DEBIAN-CVE-2026-89863, GHSA-43g8-fhx4-jf78, UBUNTU-CVE-2026-89863

## What is CVE-2026-89863?

CVE-2026-89863 is a high-severity vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check

qla_chk_edif_rx_sa_delete_pending() obtains the SCSI command via
GET_CMD_SP(sp) and immediately dereferences cmd->sc_data_direction.
That command pointer can be NULL: the firmware may post a status
completion for a command that has already been returned or aborted.  The
caller qla2x00_status_entry() acknowledges this on the very same status
path, re-fetching GET_CMD_SP(sp) and bailing out with the "Command
already returned" message when it is NULL -- but that check runs only
after qla_chk_edif_rx_sa_delete_pending() has already dereferenced the
pointer, so a NULL cmd crashes the kernel in interrupt context.

Return early when cmd is NULL, before touching cmd->sc_data_direction.

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


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

Apply the vendor's patch.

## Is CVE-2026-89863 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89863 is a high-severity vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89863 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-89863/ (Markdown: https://insights.sbomify.com/CVE-2026-89863/index.md)
```

## Sources

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

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