[CVE-2026-89863][MODERATE REGULAR] scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-89863
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check
Commit: e479e9b148456905d12711411484b94083c8ff58
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e479e9b148456905d12711411484b94083c8ff58
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89863
Analysis date: Wed, 16 Sep 2026 11:57:55 -0400
ActionableScore: 3
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
A NULL pointer dereference in the qla2xxx EDIF status path can crash the kernel in interrupt context when firmware reports completion for an already returned or aborted SCSI command before cmd is validated.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-89863 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89863

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE REGULAR
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-89863	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-89863 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-703;CWE-362;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '6.5';DESCR 'A NULL pointer dereference in the qla2xxx EDIF status path can occur because qla_chk_edif_rx_sa_delete_pending reads cmd sc_data_direction before checking whether GET_CMD_SP returned NULL. The NULL command state can happen when firmware reports a status completion for a SCSI command that was already returned or aborted, causing a kernel crash in interrupt context. For the CVSS the PR:N is used for the higher risk interpretation because an attacker does not need local privileges on the host if the condition can be induced from an adjacent storage fabric or malicious FC endpoint. The issue is not reachable from the public Internet and normally requires access to a Fibre Channel or storage network plus affected qla2xxx EDIF deployment conditions. Impact is denial of service via kernel crash. No clear information leak or privilege escalation primitive is visible from the patch because the observed primitive is a NULL pointer dereference rather than UAF or overwrite.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3)	YES	DANGER NULLPTR SIMPLEFIX HARDWARE LINUS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=3
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

## 1. ActionableScore

* Raw conservative score: 3
* Conservative score: 3
* Raw paranoid score: 3
* Paranoid score: 3
* Final recommended bucket: **Borderline / manual review recommended**::

No floor or cap changed the score.

## 2. Signal breakdown

Positive signals:

* +1 Firmware-mediated external influence: the invalid completion state is produced through qla2xxx firmware/status completion handling, and attacker relevance would likely require influence from a Fibre Channel/storage fabric endpoint or a faulty/malicious device path.
* +1 Reliable kernel crash / strong DoS: the commit states that the NULL command pointer is dereferenced in interrupt context and crashes the kernel.
* +1 Important storage path: the bug is in the SCSI qla2xxx EDIF status completion path, which is a storage I/O subsystem path where host crash is operationally significant.

Non-awarded signals:

* Real UAF not awarded: the patch shows GET_CMD_SP(sp) can return NULL and the code dereferences NULL. It does not establish a dangling non-NULL command pointer being used after free.
* Concrete repeated release/refcount not awarded: there is no first put/release followed by a second lifetime mutation on the same reference.
* Controlled reclaim not demonstrated.
* Arbitrary or directed write not demonstrated.
* Confidentiality and integrity not awarded: the primitive is a NULL pointer dereference, not disclosure, overwrite, or useful object corruption.
* Direct remote/network +2 not awarded: firmware/device mediation and Fibre Channel deployment assumptions are material.
* Extra availability not awarded: the same kernel crash is already counted once.
* Race/timing penalty not applied: the issue is an invalid ordered completion state, but supplied evidence does not establish a narrow attacker-uncontrollable race.
* Hardware rarity penalty not applied: qla2xxx/FC/EDIF prerequisites are noted in reachability, but the prompt requires concrete evidence before subtracting merely because this is a driver path.

## 3. Reachability analysis

The vulnerable path is reached when qla_chk_edif_rx_sa_delete_pending() handles a status completion and reads cmd->sc_data_direction before validating that GET_CMD_SP(sp) returned a non-NULL command. The commit states that firmware may post a completion for a command that has already been returned or aborted.

The evaluated practical attacker model is unresolved/fabric-mediated. A malicious or faulty Fibre Channel endpoint, storage fabric condition, or device/firmware behavior may be relevant, but the supplied evidence does not fully prove that an ordinary remote attacker can deterministically create the NULL command state. It is not public-Internet reachable in the usual sense.

HostAdminRequired is UNKNOWN because the complete trigger may be possible through external storage-fabric influence, but the supplied evidence does not prove a complete below-host-admin attacker path. It also does not prove that host administrator privileges are required.

NamespaceScopedPrivilege is NO because no user namespace or network namespace capability path is involved.

Prior setup likely includes affected qla2xxx hardware, EDIF code path availability, and relevant SCSI/Fibre Channel operation. These are deployment prerequisites, not enough by themselves to apply a rare-hardware penalty.

## 4. Primitive and severity interpretation

The exact primitive is a NULL pointer dereference in qla_chk_edif_rx_sa_delete_pending() caused by using cmd->sc_data_direction before checking cmd. This is CLASS_C invalid-state/crash behavior.

This is not active structured UAF. The pointer is NULL rather than a stale non-NULL object whose fields are consumed after lifetime end. The patch only adds an early return when cmd is NULL.

There is no concrete repeated release/refcount operation. There is no evidence that the first lifetime operation may free an object and that the same exact reference later reaches a second put/free/refcount mutation.

Demonstrated consequence is kernel crash in interrupt context, i.e. denial of service. Speculative consequences beyond DoS are not supported by the patch. There is no meaningful exploitation leverage beyond crash shown by the supplied context.

ImportantCandidate is NO because this is a crash-only NULL dereference without UAF, overwrite, controlled reclaim, authorization bypass, or boundary-crossing primitive. ManualReview is still RECOMMENDED because the trigger is firmware/storage-fabric mediated and the affected path is a kernel storage driver interrupt/status path.

AutoDowngradeAllowed is YES because no unresolved Class A or strong Class B primitive remains.

Likely operational severity is ordinary Moderate to borderline Actionable Moderate, depending on whether the affected system exposes the qla2xxx EDIF storage path to untrusted or semi-trusted Fibre Channel fabric participants.

## 5. One-sentence report phrase

A NULL pointer dereference in the qla2xxx EDIF status path can crash the kernel in interrupt context when firmware reports completion for an already returned or aborted SCSI command before cmd is validated.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the established primitive is crash-only, but the affected path is a storage fabric driver completion path and the practical attacker reachability depends on Fibre Channel, EDIF, firmware, and deployment conditions that should be checked manually.

## 7. Call-site confidence

Call-site confidence: medium

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check
Commit: e479e9b148456905d12711411484b94083c8ff58
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e479e9b148456905d12711411484b94083c8ff58

Commit description:

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.

Fixes: dd30706 ("scsi: qla2xxx: edif: Add key update")
Cc: stable@vger.kernel.org
Signed-off-by: Nilesh Javali <njavali@marvell.com>
Reviewed-by: Hannes Reinecke <hare@kernel.org>
Link: https://patch.msgid.link/20260723050413.3897522-47-njavali@marvell.com
Signed-off-by: Martin K. Petersen (Oracle) <mkp@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/scsi/qla2xxx/qla_edif.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e479e9b148456905d12711411484b94083c8ff58

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-89863 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89863

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 6.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 3

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).