[CVE-2026-89844][MODERATE 7.0] scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition

[CVE-2026-89844][MODERATE 7.0] scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition

[AL-KERNEL]

CVE: CVE-2026-89844
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition
Commit: e8f1b0cb9782338c6341ceed816e9c1243743cdd
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e8f1b0cb9782338c6341ceed816e9c1243743cdd
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89844
Analysis date: Wed, 16 Sep 2026 06:58:37 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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 7.0
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-89844	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-89844 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:L/I:L/A:H';CWE-362;CWE-667;*CWE-664;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '6.4';DESCR 'qla2xxx report ID acquisition can update the host_map btree without holding vport_slock in the format 1 path, while the same map is also modified by other serialized paths. Concurrent btree_insert32, btree_update32, or btree_remove32 operations can race and corrupt the host_map data structure. For the CVSS the PR:N is used for the paranoid adjacent fabric scenario because an attacker may not need local code execution on the victim if they can influence Fibre Channel fabric events, but practical exploitation usually requires access to the same FC SAN or control of storage fabric behavior. The issue is not directly Internet reachable over TCP/IP by itself. Impact is at least denial of service through kernel crash or storage path disruption, and in worst case may allow limited confidentiality or integrity impact due to kernel data structure corruption and should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5)	YES	LOCK SIMPLEFIX RACE HARDWARE LINUS  KPANIC INCREASED_TO_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4	NO	NO	checked

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

ActionableScore=5
ActionableScoreLower=4
PrimitiveClass=CLASS_B
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=YES
ManualReview=REQUIRED
AutoDowngradeAllowed=NO

1. ActionableScore

* Raw conservative score: 4
* Conservative score: 4
* Raw paranoid score: 5
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

No floor or cap was applied.

2. Signal breakdown

Conservative signals:

* +1 Weak / indirect kernel corruption candidate: `qla_update_host_map()` reaches `qla_update_vp_map()`, which mutates `ha->host_map` btree via `btree_insert32()`, `btree_update32()`, and `btree_remove32()` without the documented required `vport_slock`.
* +1 Reliable kernel crash / strong DoS concern: corruption of an active driver btree used for FC host mapping can plausibly lead to kernel fault, driver malfunction, or storage path disruption.
* +1 Important storage path: this is in the SCSI qla2xxx Fibre Channel storage path, where host map corruption can affect storage connectivity and device discovery.
* +1 Firmware / fabric mediated external influence: the affected path handles report ID acquisition from the adapter / fabric side rather than a purely local software-only operation.

Paranoid additional signal:

* +1 Weak exploitation concern: the corrupted object is an active lookup btree used for host / vport mapping, so unresolved effects may go beyond an immediate crash and can affect object selection or traversal. This is not enough for CLASS_A.

Non-awarded material signals:

* Controlled reclaim not demonstrated.
* Arbitrary write not demonstrated.
* Real UAF not established.
* Concrete repeated release / refcount operation not established.
* Confidentiality and integrity points are not awarded directly. The btree corruption gives unresolved concern, but no concrete disclosure, arbitrary write, credential overwrite, or privilege escalation primitive is shown.
* Remote Internet reachability is not established. This is not a generic TCP/IP remote bug.
* No race penalty was subtracted merely because the bug is a race. The evidence does not prove a narrow one-shot or externally uncontrollable timing window.
* No host-admin penalty was applied because host-admin-equivalent privilege is not positively established for the complete trigger.
* No rare-hardware penalty was applied merely because this is a driver. Fibre Channel is specialized, but the prompt requires concrete evidence before subtracting for rare physical-only exposure.

Repeated release / refcount checklist:

* First release can end lifetime: not applicable.
* Exact same reference survives: not applicable.
* Second operation mutates lifetime / refcount: not applicable.
* +1 Concrete repeated release / refcount: not awarded.
* Paranoid repeated-refcount leverage +1: not awarded.
* FLOOR 5 for repeated release: not applied.

3. Reachability analysis

The vulnerable operation is reached during `qla24xx_report_id_acquisition()` format-1 handling, where the driver updates the host map after taking a vport reference but without holding `ha->vport_slock`.

The most plausible attacker influence is adjacent to the Fibre Channel SAN / fabric or mediated through adapter / firmware events that cause report ID acquisition and concurrent host map updates. This supports an adjacent / fabric-mediated model rather than direct Internet reachability.

A purely local ordinary-user trigger is not established by the supplied evidence. A host-admin-only requirement is also not positively established, because the input describes a driver path processing external acquisition events rather than an explicit privileged ioctl or sysfs-only control path.

HostAdminRequired is therefore UNKNOWN.

NamespaceScopedPrivilege is NO because this is not a namespace-scoped networking or container capability path. The complete operation is tied to physical / virtualized FC adapter state, not attacker-created namespaces.

Prior host setup likely exists in practice because the qla2xxx driver and hardware must be present and active. This is a deployment prerequisite, but not scored as a negative rare-hardware penalty without stronger evidence that the configuration is unusual or physical-only in the evaluated product.

Race repeatability is unresolved. The race requires concurrent host map updates, but the patch does not establish that timing is exceptionally narrow or one-shot.

4. Primitive and severity interpretation

The exact primitive is an unlocked concurrent mutation of an active kernel btree, `ha->host_map`, in the qla2xxx driver.

This is not a UAF and not a fixed stale-storage case. It is active kernel data-structure corruption caused by a missing lock around a documented serialized update path.

The demonstrated consequence is corruption of the host map btree, with realistic availability impact through kernel crash, driver failure, or Fibre Channel storage path disruption.

The speculative consequence is that corrupted btree state may affect later traversal or object selection in ways not fully shown by the small patch. That supports CLASS_B and manual review, but not CLASS_A because controlled target selection, controlled payload, arbitrary write, controlled reclaim, callback control, or LPE is not established.

PrimitiveClass is CLASS_B because a real active kernel tree/object corruption primitive is established, but exploitation leverage remains unresolved.

ImportantCandidate is YES because the corrupted object is active driver state in an important storage path and automatic downgrade would discard an unresolved kernel corruption primitive.

AutoDowngradeAllowed is NO because this is not merely a warning, leak, or crash-only invalid dereference. The patch-supported root cause is unsynchronized mutation of an active btree, and the post-corruption effects require manual review.

Likely operational severity is Actionable Moderate, with Strong Important candidacy requiring manual review if downstream btree corruption can be connected to stronger memory corruption, object confusion, or privilege/security impact.

5. One-sentence report phrase

qla2xxx report ID acquisition can update the active host_map btree without vport_slock, allowing concurrent host map updates to corrupt driver state and potentially cause a kernel crash or Fibre Channel storage path disruption.

6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch establishes active kernel btree corruption in a storage driver, and the downstream effects of corrupted host_map traversal or object selection are not sufficiently resolved for automatic downgrade.

7. Call-site confidence

Call-site confidence: high

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

Patch: scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition
Commit: e8f1b0cb9782338c6341ceed816e9c1243743cdd
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e8f1b0cb9782338c6341ceed816e9c1243743cdd

Commit description:

qla24xx_report_id_acquisition() format-1 handling drops vport_slock after
taking the vport reference and then calls qla_update_host_map() without
the lock. That reaches qla_update_vp_map(), which mutates the ha->host_map
btree via btree_insert32()/btree_update32()/btree_remove32() and is
documented to require vport_slock to be held by the caller. Running it
unlocked can race concurrent host_map updates and corrupt the btree.

The format-2 path in the same function already wraps its host_map update
(SET_AL_PA) in vport_slock; the format-1 path is the lone outlier.

Hold vport_slock across the format-1 qla_update_host_map() call to honor
the documented locking contract. The vref_count taken in the loop keeps
the vport valid, so this only adds the missing host_map serialization.

Fixes: 430eef0 ("scsi: qla2xxx: Relocate/rename vp map")
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-24-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_mbx.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=e8f1b0cb9782338c6341ceed816e9c1243743cdd

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

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

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

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: 4
  Paranoid ActionableScore: 5

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: YES
Published priority for this report (same as in Subject): MODERATE 7.0

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