[CVE-2026-89842][MODERATE REGULAR] scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started

[CVE-2026-89842][MODERATE REGULAR] scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started

[AL-KERNEL]

CVE: CVE-2026-89842
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started
Commit: 2935b730211c5c1433aa6101fa3b55df2b63869a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2935b730211c5c1433aa6101fa3b55df2b63869a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89842
Analysis date: Wed, 16 Sep 2026 11:44:20 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-89842	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-89842 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';CWE-703;CWE-754;*CWE-664;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.3';DESCR 'qla2xxx NVMe/FC LS response handling can emit an LS reject IOCB when firmware is not started and then ring the firmware doorbell through MMIO during a reset or EEH window. A fabric attached peer may influence this path by sending unsolicited NVMe LS traffic while the adapter firmware is stopped or resetting, but reliable triggering depends on the reset timing and the Fibre Channel storage fabric state. For the CVSS the PR:N is used for the paranoid score because an attacker does not need privileges on the target host if they can send NVMe/FC LS traffic from the attached storage fabric. The issue is not Internet reachable in the usual IP sense and is limited to systems using qla2xxx NVMe/FC on a reachable storage fabric. Impact is denial of service through adapter reset disruption, failed I/O, or possible host side storage path instability. No direct UAF, OOB access, information disclosure, or privilege escalation primitive is indicated by the code change.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3)	YES	LOCK SIMPLEFIX NVME HARDWARE LINUS  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	NO	NO	checked

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

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

1. ActionableScore

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

No floor or cap changed the score.

2. Signal breakdown

Conservative signals:

* +1 Firmware mediated or fabric mediated external influence. The vulnerable path can be influenced by NVMe/FC LS traffic from a fabric attached peer, but the HBA firmware and storage fabric are material to the path.
* +1 Invalid active device state operation. The driver may submit an LS reject IOCB and ring the firmware doorbell while firmware is not started.
* +1 Availability impact realistic. The effect can disrupt adapter reset handling, I/O progress, or storage path stability.
* -1 Special timing or state window. The issue requires fw_started to be clear, typically during reset or EEH handling.

Paranoid difference:

* The paranoid score withholds the -1 timing reduction because repeated unsolicited LS traffic combined with naturally occurring reset or recovery windows makes the state condition plausible enough for manual triage.

Important non-awarded signals:

* No Real UAF is established.
* No OOB access is established.
* No arbitrary or directed kernel write is established.
* No controlled reclaim or object replacement is demonstrated.
* No confidentiality or integrity impact is awarded.
* No privilege escalation primitive is indicated.
* Direct Internet remote reachability is not established.
* Extra availability is not separately awarded beyond the same storage path disruption.

3. Reachability analysis

The evaluated attacker is a fabric attached peer that can send NVMe/FC LS traffic to a system using qla2xxx NVMe/FC. This does not require privileges on the target host, so HostAdminRequired is NO for the fabric attacker model.

The issue is not reachable through ordinary IP networking. It is adjacent to a Fibre Channel or NVMe/FC storage fabric and depends on the qla2xxx driver and compatible HBA environment.

Namespace scoped privilege is not relevant here. There is no evidence that Linux user or network namespaces provide the complete trigger path.

A prior host configuration is required in the deployment sense: the system must use qla2xxx NVMe/FC and expose the relevant fabric path. I did not apply a hardware rarity penalty because the patch itself is in a hardware driver, and the scoring rules require concrete evidence before using strong hardware reductions.

The main reliability constraint is the firmware reset or EEH window where fw_started is false. Conservative scoring treats this as a timing/state limitation. Paranoid scoring treats it as reachable enough for manual review because reset and recovery windows can occur in real storage deployments.

4. Primitive and severity interpretation

The exact primitive is an invalid device/firmware state transition: the driver queues an IOCB and writes the firmware doorbell while firmware is not started.

This is not an active structured kernel UAF and not fixed stale storage. It is a Class C invalid-state / DoS issue in a storage driver.

There is no concrete repeated release or refcount operation. There is no first lifetime operation that can free an object followed by a second lifetime mutation on the same dangling reference.

The demonstrated consequence is denial of service or degraded availability of the adapter or storage path. A host-wide crash, memory corruption, information disclosure, and privilege escalation are not established by the patch.

ImportantCandidate is NO because the patch shows device state misuse and availability impact, but not a kernel corruption, ownership, lifetime, authorization, or semantic reinterpretation primitive with unresolved Important-grade leverage.

AutoDowngradeAllowed is YES because this is Class C with no unresolved corruption or security-boundary primitive. Manual review is still recommended because the issue is externally influenced from a storage fabric and affects kernel storage reset behavior.

5. One-sentence report phrase

qla2xxx can ring the firmware doorbell and queue an NVMe/FC LS reject IOCB while firmware is stopped or resetting, allowing a fabric attached peer under reset timing conditions to cause storage path denial of service without target host privileges.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the issue is not memory corruption or privilege escalation, but it is externally influenced from a storage fabric and affects a kernel storage driver reset path.

7. Call-site confidence

Call-site confidence: medium

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

Patch: scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started
Commit: 2935b730211c5c1433aa6101fa3b55df2b63869a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2935b730211c5c1433aa6101fa3b55df2b63869a

Commit description:

qla_nvme_xmt_ls_rsp() bails out to the out: label when firmware is not
started (!ha->flags.fw_started), but the out: path unconditionally calls
qla_nvme_ls_reject_iocb(), which ends in qla2x00_start_iocbs() and an
unconditional doorbell write to the request queue in-pointer register.
This rings the firmware doorbell and queues an IOCB that stopped or
resetting firmware cannot consume, and touches MMIO during the reset/EEH
window where fw_started is also clear.

Only emit the LS reject IOCB (and ring the doorbell) when fw_started is
set; otherwise just clean up and return. The post-allocation failure
cases (SRB alloc / qla2x00_start_sp() failure) run with firmware started
and still send the reject. Apply the same guard to the reject emission
in qla2xxx_process_purls_pkt().

Fixes: 875386b ("scsi: qla2xxx: Add Unsolicited LS Request and Response Support for NVMe")
Cc: stable@vger.kernel.org
Reported-by: Sashiko <sashiko-dev@google.com>
Signed-off-by: Nilesh Javali <njavali@marvell.com>
Link: https://patch.msgid.link/20260730155838.2119230-26-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_nvme.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=2935b730211c5c1433aa6101fa3b55df2b63869a

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

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

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:L
  The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.3

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: 2
  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).