[CVE-2026-97527][MODERATE 7.0] scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock [ Upstream

[CVE-2026-97527][MODERATE 7.0] scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock [ Upstream

[AL-KERNEL]

CVE: CVE-2026-97527
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock [ Upstream
Commit: b211d138cad86f749826d6132db6388eded992d8
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b211d138cad86f749826d6132db6388eded992d8
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97527
Analysis date: Fri, 25 Sep 2026 09:08:21 -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-97527 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97527

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-97527	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-97527 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:H/I:H/A:H';CWE-362;*CWE-416;CWE-415;CWE-119;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7.5';DESCR 'A race condition in the qla2xxx NVMe FC unsolicited context handling can corrupt the fcport unsol_ctx_head list because ISR DPC worker NVMe transport callback and completion paths modify the list without a common lock. Concurrent insertion and removal or two concurrent removals can corrupt list pointers and may result in use after free double free kernel memory corruption or a kernel crash. For the CVSS the PR:N because the attacker does not need local privileges on the target host, but must have access to the relevant Fibre Channel SAN fabric and be able to generate NVMe FC traffic. The attack vector is adjacent AV:A rather than Internet reachable AV:N. The race requires timing between concurrent processing contexts so AC:H is appropriate. Impact is at least denial of service and the memory corruption nature of the bug provides a plausible path to confidentiality integrity impact or privilege escalation. YES REQUIRES MANUAL CHECK.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5)	YES	LOCK DEADLOCK INIT SIMPLEFIX 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=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
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**::

2. Signal breakdown

* +2 Real UAF or active lifetime violation. The patch establishes that the same per-fcport unsolicited-context list can be concurrently removed from multiple asynchronous paths. Each relevant removal path performs list_del followed by kfree of the context. A concurrent removal can therefore operate on an element whose list state or object lifetime was already changed by another removal path.
* +1 Concrete repeated release or free operation. The visible delete paths all execute list_del and then kfree on uctx. The commit explicitly identifies two concurrent delete paths as possible. One path can free the context while another path still holds and subsequently frees the same context.
* +1 Firmware-mediated external influence. NVMe FC unsolicited LS traffic is processed through the QLogic response queue ISR and adapter firmware or hardware event path. A peer on the relevant Fibre Channel fabric can plausibly influence the request sequence, but the vulnerable operation is not a direct Internet protocol parser.
* +1 Reliable kernel crash or strong DoS. Corrupted list pointers, post-free list operations, or double kfree can cause a kernel fault, allocator corruption detection, or panic.
* -1 Hard timing requirement. Triggering requires an overlap between ISR processing, DPC or purex work, NVMe FC transport handling, or SRB completion. The supplied patch does not establish that an external peer can deterministically schedule these host-side contexts.

Paranoid-only signal:

* +1 Unresolved post-free lifetime mutation. The second kfree is a concrete lifetime-mutating operation through a context whose lifetime may already have ended. This is stronger than an ordinary stale read or immediate poisoned-pointer fault, although controlled reclaim or allocator manipulation is not demonstrated.

Important non-awarded signals:

* Controlled reclaim or attacker-controlled replacement object is not demonstrated.
* Arbitrary or directed kernel write is not demonstrated.
* Confidentiality impact is not awarded. No disclosure path is shown.
* Integrity impact is not awarded. No controlled modification of protected state is shown.
* Strong LPE plausibility is not separately awarded. A double free and list corruption alone do not prove credential manipulation, callback control, or controlled type confusion.
* Direct remote reachability bonus is not awarded. The input reaches the driver through Fibre Channel adapter response processing and is better classified as firmware-mediated external influence.
* No rare-hardware penalty is applied. Fibre Channel and QLogic adapters are specialized, but the patch supports a realistic deployed enterprise SAN scenario and does not establish a physical-only attack.
* No additional Availability point is awarded because the same kernel crash or allocator failure is already counted once.

Repeated lifetime analysis:

* First release can end lifetime: Yes. Each visible removal path calls kfree on uctx.
* Exact reference survives: Directly implied. Concurrent deletion paths can retain references to the same unsolicited context while another path deletes and frees it.
* Second operation mutates lifetime state: Yes. The later path can execute list_del and kfree on the same context.
* Concrete repeated release or free signal awarded: Yes, +1.
* Paranoid post-free lifetime mutation awarded: Yes, +1.
* FLOOR 5 applied: No. The conservative score remains 4 because the external trigger is mediated through a specialized FC adapter path and requires a timing-sensitive concurrent sequence. The paranoid score reaches 5 from the concrete unresolved second free operation.

3. Reachability analysis

The evaluated attacker is a peer able to send or induce NVMe FC unsolicited LS traffic on the same Fibre Channel SAN fabric as the affected QLogic qla2xxx adapter. The vulnerable flow enters through response queue processing and interacts with host-side DPC work, NVMe FC transport callbacks, and SRB completion paths.

Host administrator privilege on the victim is not positively required by the supplied patch. However, below-host-admin reachability is also not fully proven because FC zoning, NVMe FC session establishment, initiator authorization, and the ability to generate the required unsolicited LS traffic are not shown. Therefore HostAdminRequired is UNKNOWN.

Namespace-scoped privilege is UNKNOWN. The affected resource is a physical or host-managed Fibre Channel adapter and fcport state. There is no evidence that an attacker-created network namespace can create the QLogic adapter state, establish the NVMe FC path, and perform the complete trigger sequence.

A prior administrator must deploy the affected QLogic adapter and NVMe FC environment. This is a deployment prerequisite, not proof that the attacker needs host-admin privileges once such a fabric is available. The race may be repeatable by generating relevant FC traffic, but the patch does not establish reliable attacker control over the host ISR, workqueue, transport callback, and completion timing.

4. Primitive and severity interpretation

The primitive is concurrent corruption of an active kernel list containing unsolicited NVMe FC context objects. The list is an active structured kernel object, not fixed stale DMA storage. Multiple paths remove list elements and free their uctx objects without a common lock.

This is more serious than an ordinary stale cleanup dereference because the affected paths perform a second concrete lifetime-mutating operation. One path can execute list_del and kfree, ending the lifetime of uctx, while another concurrent path can still execute list_del and kfree through its stale reference. The patch directly adds a shared spinlock around every list_add_tail and list_del operation to prevent this condition.

The issue is CLASS_B. A real lifetime violation and potential double free are directly implied, but controlled reclaim, controlled list-pointer target selection, arbitrary write, callback dispatch, information disclosure, and privilege escalation are not established. The demonstrated practical consequence is kernel crash or denial of service. The speculative consequence is allocator or list corruption that could be exploitable under favorable reuse conditions.

ImportantCandidate is YES because concurrent list corruption combined with a possible second kfree leaves meaningful post-lifetime corruption leverage unresolved. AutoDowngradeAllowed is NO because automatically treating the issue as ordinary crash-only behavior would discard a concrete kernel lifetime-corruption primitive. The likely operational severity is Actionable Moderate, with Important-level review warranted for deployments where untrusted or semi-trusted FC peers can access the same NVMe FC fabric.

5. One-sentence report phrase

A race in qla2xxx NVMe FC unsolicited context handling can cause concurrent list deletion and kfree of the same context, resulting in list corruption, use after free, double free, and possible kernel denial of service from an attacker able to influence NVMe FC traffic on the affected Fibre Channel fabric.

6. Manual review recommendation

MANUAL CHECK REQUIRED

The patch establishes an active kernel list corruption and possible concurrent double free, but the degree of attacker control over FC traffic, adapter-mediated event delivery, object reuse, and post-free allocator state requires deployment-specific review.

7. Call-site confidence

Call-site confidence: medium

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

Patch: scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock [ Upstream
Commit: b211d138cad86f749826d6132db6388eded992d8
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b211d138cad86f749826d6132db6388eded992d8

Changed files:
  drivers/scsi/qla2xxx/qla_def.h
  drivers/scsi/qla2xxx/qla_init.c
  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=b211d138cad86f749826d6132db6388eded992d8

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

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

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