[CVE-2026-89861][MODERATE 7.0] scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition()

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

CVE: CVE-2026-89861
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition()
Commit: d09ef32af1e05d79f29b460521a20bc4e6fd2ecf
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d09ef32af1e05d79f29b460521a20bc4e6fd2ecf
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89861
Analysis date: Wed, 16 Sep 2026 06:54:26 -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-89861 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89861

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-89861	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-89861 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-362;CWE-667;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7';DESCR 'A race in qla24xx_report_id_acquisition can leave a qla2xxx virtual port pointer unprotected after it is found on ha vp_list. A concurrent qla24xx_deallocate_vp_id can tear down and free the same vport before later code updates host mapping and sets flags through that stale pointer. This is a use after free in kernel driver state and can cause at least a local denial of service via crash. In the worst still defensible case, the stale pointer writes may allow broader memory corruption impact, so confidentiality and integrity are treated as high in the paranoid score. For the CVSS the PR:L is used for the paranoid score because some deployments may delegate NPIV or storage administration to reduced capability root, container root, or service accounts rather than full host administrators. The issue is not directly reachable over normal IP networking, but Fibre Channel fabric events and SAN access may be relevant to triggering the vulnerable path. Impact may include kernel crash and possible privilege escalation, therefore this finding should be manually reviewed.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5)	YES	UAF HARDWARE LINUS KPANIC 	NO	NO	guess

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

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

1. ActionableScore

* Raw conservative score: 3
* Conservative score: 4
* Applied conservative floor/cap: Real UAF floor 4 applied because a stale vport pointer is used after possible free, the stale use is not fixed stale storage, and host-admin-equivalent reachability is not positively established.
* Raw paranoid score: 5
* Paranoid score: 5
* Applied paranoid floor/cap: none
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

Conservative positive signals:

* +2 Real UAF / active lifetime violation. The vport is found under vport_slock, the lock is dropped, no reference is held, and qla24xx_deallocate_vp_id can free the same vport before later use.
* +1 Reliable kernel crash / strong DoS. A stale freed vport is passed to qla_update_host_map and then modified via set_bit operations, which can plausibly fault or corrupt freed kernel object storage.

Conservative negative signals:

* No -2 host-admin penalty. Host-admin-equivalent privilege is not positively established from the supplied patch.
* No -1 race penalty. The bug is a race, but the supplied evidence does not prove a narrow one-shot or externally uncontrollable timing window sufficient for a scoring penalty.
* No hardware rarity penalty. qla2xxx is hardware-specific, but the supplied evidence does not establish rare physical-only access as a required attacker prerequisite.

Paranoid additional signals:

* +1 Weak exploitation / corruption concern. The stale use is not only a read or immediate cleanup fault. The code calls qla_update_host_map and writes VP_IDX_ACQUIRED, REGISTER_FC4_NEEDED, and REGISTER_FDMI_NEEDED through the potentially freed structured vport.
* +1 Firmware-mediated external influence. The vulnerable path processes Fibre Channel ID acquisition state mediated by the adapter and SAN fabric, which may matter to practical triggering, but this is not direct IP network reachability.

Important non-awarded signals:

* Controlled reclaim not demonstrated.
* Arbitrary or directed kernel write not demonstrated.
* Callback or function-pointer control not demonstrated.
* Local unprivileged trigger not established.
* Direct remote network reachability not established.
* Concrete repeated release/refcount signal not awarded. The patch adds a missing temporary reference, but it does not show a first release followed by a second lifetime-mutating operation on the exact same dangling reference.
* Structured stale-object leverage beyond the weak concern is not awarded because attacker-controlled replacement or attacker-shaped post-free contents are not established.
* Extra Availability not awarded because the same crash/DoS is already counted.
* Confidentiality and integrity bonuses are not awarded as separate ActionableScore signals because no disclosure, protected-object write, credential manipulation, or controlled corruption primitive is demonstrated.

Repeated release/refcount checklist:

* First release can end lifetime: qla24xx_deallocate_vp_id can tear down and free the vport, but this is the concurrent deallocation path, not an earlier release in the same control flow.
* Exact same reference survives: yes, vp remains in qla24xx_report_id_acquisition after the lock is dropped.
* Second operation is a real lifetime/refcount mutation: no. The stale operations are qla_update_host_map and flag writes, not a second put/release/refcount mutation on the same reference.
* +1 Concrete repeated release/refcount awarded: no.
* Paranoid repeated-refcount leverage +1 awarded: no.
* FLOOR 5 applied: no. The UAF is meaningful, but the specific FLOOR 5 repeated-release condition is not met.

3. Reachability analysis

The vulnerable path is in the qla2xxx Fibre Channel driver, specifically the NPIV virtual-port handling path in qla24xx_report_id_acquisition. The triggering condition requires an ID acquisition report path to find a vport and then race with qla24xx_deallocate_vp_id tearing down that same vport before later use.

A normal remote IP attacker is not shown to reach this path. Fibre Channel fabric events or SAN-side behavior may influence the report path, but device and firmware mediation is material, so this is not scored as direct network reachability.

The complete privilege boundary is unresolved. Creating, deleting, or managing NPIV vports is commonly an administrative or delegated storage-management operation, but the supplied evidence does not positively establish that full host-admin-equivalent privilege is always required for the complete trigger. Therefore HostAdminRequired is UNKNOWN rather than YES.

No namespace-scoped capability path is established. This is not a network-namespace or container-local object in the supplied evidence, so NamespaceScopedPrivilege is NO.

Prior setup likely includes qla2xxx-capable hardware and NPIV/vport configuration. This affects practical exposure, but the supplied evidence does not justify a rarity penalty. Race repeatability is uncertain. The race is real, but no evidence proves it is a hard one-shot race.

4. Primitive and severity interpretation

The exact primitive is a real use-after-free of a qla2xxx virtual port object. The stale object is an active structured kernel object, not fixed stale DMA storage. The stale use occurs in an active event/report handling path, not merely in final cleanup or destructor-only code.

The code may use the freed vport in qla_update_host_map and then writes flags through the stale pointer. This is stronger than an ordinary stale read that immediately faults, but weaker than a demonstrated controlled reclaim, arbitrary write, refcount takeover, or callback hijack.

PrimitiveClass is CLASS_B. It is a real active-object lifetime bug with post-free structured use, but the supplied evidence does not establish CLASS_A exploitation leverage.

Demonstrated consequence is at least kernel memory corruption risk and likely local or fabric-mediated denial of service through crash. Speculative consequence is broader memory corruption or privilege escalation if an attacker can influence reuse or replacement, but that is not established by the patch.

ImportantCandidate is YES because the UAF is concrete, the stale operations include writes to freed structured object state, and exploitation leverage beyond crash remains unresolved. AutoDowngradeAllowed is NO because automatically closing it as ordinary crash-only Moderate would discard a concrete active-object UAF with meaningful unresolved post-lifetime corruption behavior.

Likely operational severity is Actionable Moderate, with Important-vs-Moderate manual review required.

5. One-sentence report phrase

A race in qla24xx_report_id_acquisition can leave a qla2xxx vport pointer without a lifetime reference after lookup, allowing concurrent vport teardown to free the object before later host-map updates and flag writes use the stale pointer, causing at least a kernel crash and requiring manual review for possible broader memory corruption impact.

6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch directly establishes a real UAF of an active structured kernel driver object, and later code writes through the potentially freed pointer. Controlled reclaim and LPE are not proven, but the primitive is too strong for automatic downgrade.

7. Call-site confidence

Call-site confidence: medium

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

Patch: scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition()
Commit: d09ef32af1e05d79f29b460521a20bc4e6fd2ecf
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d09ef32af1e05d79f29b460521a20bc4e6fd2ecf

Commit description:

In the format 1 path, the virtual port is located on ha->vp_list while
holding vport_slock, but the lock is dropped before vp is used:
qla_update_host_map() is called and VP_IDX_ACQUIRED/REGISTER_FC4_NEEDED/
REGISTER_FDMI_NEEDED are set on vp. No reference is taken across that
window, so a concurrent qla24xx_deallocate_vp_id() can tear the vport
down and free it, leading to a use-after-free.

Take a vport reference (vref_count) under vport_slock when the matching
vp is found, and drop it after the last use of
vp. qla24xx_deallocate_vp_id() waits for vref_count to reach zero before
unlinking and freeing the vport, so the pointer stays valid. This
matches the reference idiom already used by the other ha->vp_list
traversals.

Fixes: 2c3dfe3 ("[SCSI] qla2xxx: add support for NPIV")
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-51-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=d09ef32af1e05d79f29b460521a20bc4e6fd2ecf

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

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

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

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