[CVE-2026-97537][MODERATE REGULAR] scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking [ Upstream

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

CVE: CVE-2026-97537
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking [ Upstream
Commit: f35cb67f2092b49d7949065dd56895ed47238f22
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f35cb67f2092b49d7949065dd56895ed47238f22
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97537
Analysis date: Sat, 26 Sep 2026 16:05:15 -0400
ActionableScore: 2
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-97537 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97537

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

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

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

CVE-2026-97537	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-97537 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:N/A:H';CWE-362;**CWE-476;CWE-667;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A qla2xxx queue creation failure can call dma_free_coherent with a NULL DMA ring pointer. This can cause a kernel crash on the driver error path. A separate race between queue ID reuse and queue teardown can clear a newly installed request or response queue map entry, causing inconsistent adapter queue state and possible I O failure or driver recovery failure. The issue requires a local error or recovery scenario and is not directly network reachable. For the CVSS the PR:L rating is used for the conservative score because a local service account or workload may be able to influence memory pressure or device recovery in some deployments. Typical systems may require administrative control over the adapter or driver. Impact is primarily denial of service. No concrete use after free, out of bounds access, information leak, or arbitrary write primitive is shown by this patch.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2)	YES	LOCK DANGER INIT ERRORPATH HARDWARE MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	NO	NO	checked

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

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

1. ActionableScore

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

2. Signal breakdown

* +1 Weak invalid-pointer and invalid-state concern. The error path can pass a NULL CPU ring address to dma_free_coherent after dma_alloc_coherent failure. This is an invalid DMA API invocation and can cause a kernel fault or panic.
* +1 Reliable kernel crash or strong DoS. The supplied commit explicitly states that the NULL dma_free_coherent call can panic the kernel.
* +0 Queue-map race. The locking mismatch can clobber a newly installed req_q_map or rsp_q_map entry after queue ID reuse. This establishes inconsistent queue bookkeeping and possible I O or recovery failure, but the supplied code does not establish a later stale dereference, use-after-free, arbitrary write, or host-wide fatal consequence independent of the NULL DMA-free path.
* +0 Remote reachability not established. The failure occurs in local qla2xxx queue creation and teardown logic. Firmware or fabric influence is not shown to directly reach this path.
* +0 Local unprivileged trigger not established. The input does not prove that an ordinary user can drive adapter queue creation, reset, or recovery failure.
* +0 Controlled reclaim not demonstrated.
* +0 Arbitrary or directed write not demonstrated.
* +0 Confidentiality and integrity impact not awarded. The map clobber is a bookkeeping failure, but no protected data disclosure, unauthorized modification, or attacker-controlled memory corruption primitive is demonstrated.
* +0 Extra Availability point not awarded. The queue-state inconsistency may cause I O failure or recovery problems, but this is not independently established as a persistent host-wide failure beyond the already counted potential panic.
* No race timing penalty applied. The patch demonstrates a synchronization gap, but does not establish an unusually narrow, one-shot, or externally uncontrollable timing requirement.
* No hardware-specific penalty applied. qla2xxx is a driver for Fibre Channel adapters, but driver code alone is not sufficient evidence of rare or physical-only attacker requirements.

3. Reachability analysis

The vulnerable paths are qla25xx_create_req_que and qla25xx_create_rsp_que error handling, followed by qla25xx_free_req_que or qla25xx_free_rsp_que. The first issue requires queue creation to reach a DMA allocation failure or another relevant queue-creation failure. The second issue requires a concurrent queue allocation to reuse a queue ID during the interval between bitmap clearing and later queue-map cleanup.

The supplied patch does not establish who can reliably trigger adapter queue creation, DMA allocation failure, firmware queue-creation failure, device reset, or recovery operations. It also does not establish whether such operations require host administrative privileges, delegated storage-management privileges, or can be influenced by an ordinary local workload. Therefore HostAdminRequired is UNKNOWN rather than YES or NO.

No user namespace, network namespace, capability check, container path, or namespace-local device path is shown. NamespaceScopedPrivilege is therefore UNKNOWN. No direct network attacker path is established. Fibre Channel fabric or firmware behavior may be relevant operationally, but firmware-mediated external influence is not demonstrated by the supplied evidence.

4. Primitive and severity interpretation

The primary demonstrated primitive is an invalid NULL argument passed to dma_free_coherent on an error path. The stated result can be a kernel panic, which is a host availability issue. The second primitive is a queue ID bitmap and queue-map synchronization failure. A failed queue creation can release the queue ID before its old map entry is atomically removed, allowing another creator to allocate the same ID and later have its newly installed map entry overwritten with NULL.

This is not a real UAF. The patch does not show that an object is freed while a stale reference is later dereferenced or subjected to another lifetime-mutating operation. It also does not establish a double free, refcount corruption, active-object replacement, controlled reuse, callback dispatch, or attacker-controlled DMA target.

The issue is therefore CLASS_C. The demonstrated impact is kernel crash or storage queue malfunction and I O availability degradation. A stronger consequence such as memory corruption, privilege escalation, confidentiality disclosure, or integrity compromise is speculative and is not supported by the patch context.

ImportantCandidate is NO because the patch establishes crash and invalid-state behavior, but not a meaningful unresolved kernel corruption or security-boundary primitive. AutoDowngradeAllowed is YES because no active lifetime corruption, controlled corruption, authorization bypass, or ownership violation remains unresolved from the supplied evidence.

Likely operational severity is ordinary Moderate. Systems operating affected qla2xxx adapters may wish to prioritize the fix during normal kernel maintenance, especially where adapter recovery or queue recreation is common, but the evidence does not support Important-class treatment.

5. One-sentence report phrase

A qla2xxx queue creation error can call dma_free_coherent with a NULL ring pointer and can race with queue ID reuse, causing a kernel panic or inconsistent storage queue state and denial of service.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Verify whether the affected deployment permits a non-administrative local workload, Fibre Channel initiator, management service, or firmware event to reliably induce queue creation failures or recovery operations. If no such lower-privilege path exists, this can be handled as an ordinary driver error-path DoS fix.

7. Call-site confidence

Call-site confidence: medium

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

Patch: scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking [ Upstream
Commit: f35cb67f2092b49d7949065dd56895ed47238f22
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f35cb67f2092b49d7949065dd56895ed47238f22

Changed files:
  drivers/scsi/qla2xxx/qla_mid.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=f35cb67f2092b49d7949065dd56895ed47238f22

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

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

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

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