[CVE-2026-89855][LOW] scsi: qla2xxx: Serialize flash version read in reset handler

[CVE-2026-89855][LOW] scsi: qla2xxx: Serialize flash version read in reset handler

[AL-KERNEL]

CVE: CVE-2026-89855
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: scsi: qla2xxx: Serialize flash version read in reset handler
Commit: f1fc052f2a5890ea6dba80d50254dd6258b13386
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f1fc052f2a5890ea6dba80d50254dd6258b13386
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89855
Analysis date: Wed, 16 Sep 2026 15:28:58 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
Manual review required: NO

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

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

CVE-2026-89855	LOW	https://www.kernelcve.org/list/?q=CVE-2026-89855 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L';CWE-362;CWE-667;CWE-662;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '3.6';DESCR 'The qla2xxx sysfs reset operation for updating cached versions can call get_flash_version without holding ha optrom_mutex. This can race with a concurrent VPD or optrom flash operation that uses the same hardware flash register path, causing corrupted flash version reads and inconsistent cached device information. For the CVSS the PR:L is used for the paranoid case only because some deployments may delegate HBA management to a local service account or reduced capability administrator, while the typical base case is PR:H. The issue is not network reachable and requires local control over the qla2xxx sysfs management path. Impact appears limited to integrity of cached hardware version data and possible low availability impact during management operations, not memory corruption or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0)	YES	LOCK SIMPLEFIX HARDWARE LINUS 	NO	NO	checked

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

ActionableScore=0
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=YES
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 0
* Conservative score: 0
* Raw paranoid score: 0
* Paranoid score: 0
* Final recommended bucket: **Ordinary Moderate**::

No floor or cap was applied.

2. Signal breakdown

* +0. No concrete kernel memory corruption, lifetime violation, UAF, OOB access, refcount misuse, authorization bypass, or security-boundary primitive is established.
* +0. The established issue is missing serialization around `get_flash_version()` in the qla2xxx sysfs reset path, causing potentially corrupted flash version reads.
* +0. No reliable kernel crash or host-wide DoS is demonstrated.
* +0. No confidentiality impact is established because no disclosure path is shown.
* +0. No meaningful integrity impact on protected kernel state, user data, firmware contents, or storage data is established. The integrity effect appears limited to cached hardware version information.
* +0. Race penalty not applied because a race exists, but no positive exploitability score was awarded and the issue is already non-actionable.
* +0. Host-admin/device-management access is required, but no negative score was needed because the raw score is already zero.
* Not awarded: controlled reclaim is not demonstrated.
* Not awarded: arbitrary write is not demonstrated.
* Not awarded: UAF or stale lifetime use is not demonstrated.
* Not awarded: remote reachability is not established.
* Not awarded: privilege escalation is not supported by the patch or context.
* Not awarded: extra availability impact because no crash, persistent failure, or host-wide exhaustion is shown.

3. Reachability analysis

The reachable interface is the qla2xxx sysfs reset management path for the operation described as `update cache versions without reset` with value `0x20261`.

The complete trigger appears to require local administrative control over the host device sysfs interface for a qla2xxx Fibre Channel HBA. This is host device management, not a namespaced or ordinary unprivileged interface.

HostAdminRequired is YES because writing this kind of device reset sysfs operation is host-admin-equivalent in normal kernel device-management semantics. NamespaceScopedPrivilege is NO because the physical HBA sysfs management path is not meaningfully provided by attacker-created namespaces.

No direct network trigger is established. Fibre Channel or storage traffic is not enough by itself because the bug is in the local sysfs reset path and concurrent local VPD or optrom flash operation. Prior hardware presence is required, but hardware specificity does not matter much because no security primitive is established.

Race repeatability may depend on concurrent management operations, but the demonstrated consequence is corrupted reads rather than a crash or memory corruption.

4. Primitive and severity interpretation

The exact primitive is a missing mutex around hardware flash register reads. The reset path calls `get_flash_version()` without `ha->optrom_mutex`, while the VPD update path serializes the same hardware access under that mutex.

This is a synchronization and consistency bug, not a memory-safety primitive. It is not active structured object UAF, not fixed stale storage UAF, and not a concrete repeated release or refcount mutation. The demonstrated consequence is inconsistent or corrupted cached device version data.

Speculative stronger consequences such as privilege escalation, arbitrary kernel read/write, firmware corruption, or host-wide DoS are not supported by the supplied patch. ImportantCandidate is NO because there is no unresolved kernel corruption or security-boundary primitive. AutoDowngradeAllowed is YES because this can be treated as a low-risk device-management consistency issue.

Likely operational severity is Low-like or ordinary Moderate at most.

5. One-sentence report phrase

The qla2xxx sysfs reset path can read flash version registers without holding optrom_mutex, allowing concurrent VPD or optrom operations to corrupt cached version reads, with impact limited to local privileged device-management consistency.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: no UAF, memory corruption, authorization bypass, remote trigger, or privilege-escalation path is established, and the impact appears limited to corrupted cached hardware version reads.

7. Call-site confidence

Call-site confidence: medium

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

Patch: scsi: qla2xxx: Serialize flash version read in reset handler
Commit: f1fc052f2a5890ea6dba80d50254dd6258b13386
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f1fc052f2a5890ea6dba80d50254dd6258b13386

Commit description:

The "update cache versions without reset" sysfs reset operation (0x20261)
calls get_flash_version(), which reads hardware flash registers, without
holding ha->optrom_mutex. The VPD update path serializes the same call
under optrom_mutex, so this reset path can interleave its flash register
accesses with a concurrent VPD or optrom flash operation and corrupt the
reads.

Hold ha->optrom_mutex across the get_flash_version() call to match the
VPD update path.

Fixes: 8c2cf7d ("[SCSI] qla2xxx: Add a new interface to update versions.")
Reported-by: Sashiko <sashiko-dev@google.com>
Cc: stable@vger.kernel.org
Signed-off-by: Nilesh Javali <njavali@marvell.com>
Link: https://patch.msgid.link/20260730155838.2119230-4-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_attr.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=f1fc052f2a5890ea6dba80d50254dd6258b13386

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

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

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

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: 0

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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