[CVE-2025-68741][IMPORTANT] scsi: qla2xxx: Fix improper freeing of purex item [ Upstream

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

CVE: CVE-2025-68741
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: YES
Patch: scsi: qla2xxx: Fix improper freeing of purex item [ Upstream
Commit: 8e9f0a0717ba31d5842721627ade1e62d7aec012
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8e9f0a0717ba31d5842721627ade1e62d7aec012
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2025-68741
Analysis date: Thu, 21 May 2026 16:44:42 -0400
ActionableScore: 8
ActionableScore lower bound: 5
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
An invalid free in qla2xxx PURLS IOCB error handling can pass a preallocated purex pool item to `kfree()`, potentially corrupting kernel memory in a trusted FC/NVMe storage driver path.

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

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

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: IMPORTANT
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-2025-68741	IMPORTANT	CHECK	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-590;CWE-763;*CWE-664;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7.5';DESCR 'An invalid free can occur in qla2xxx_process_purls_iocb() because an item returned by qla27xx_copy_multiple_pkt() may come from a preallocated per adapter purex pool rather than from kzalloc. The error path used kfree() directly, so a pooled item could be released through the wrong allocator path and corrupt kernel memory. For the CVSS the PR:N is used for the paranoid score because a Fibre Channel or FC/NVMe fabric peer may influence the PURLS IOCB path without a local account on the host, although practical triggering depends on qla2xxx hardware, firmware behavior, and a reachable storage fabric. The issue is not Internet remote and should be treated as adjacent or firmware mediated exposure. Impact is at least denial of service via kernel memory corruption and in worst case may allow confidentiality or integrity impact because the primitive is an invalid free in a trusted SCSI driver path.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 7)	YES	DANGER INIT SIMPLEFIX NVME ERRORPATH HARDWARE KPANIC  KPANIC INCREASED_TO_MODERATE7_BASED_ON_GUESSCVSS KPANIC INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7	NO	NO	checked

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

ActionableScore=8
ActionableScoreLower=5

## 1. ActionableScore

* Conservative score: 5
* Paranoid score: 8
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Firmware-mediated external influence: +1. The affected path processes qla2xxx FC/NVMe unsolicited request data through adapter and firmware delivered IOCBs, not a normal local syscall-only path.
* Memory corruption, strong corruption primitive: +2. The patch fixes an invalid free where a pooled `purex` item can be passed to `kfree()`.
* Real lifetime corruption: +1. The object lifetime is managed by a driver-specific pool, but the error path releases it through the wrong allocator path.
* Reliable kernel crash / strong DoS: +1. Invalid frees of pooled kernel objects can corrupt allocator or pool state and realistically crash the kernel.
* Privileged kernel/device-management memory corruption path: +1. The bug is in a trusted SCSI FC/NVMe driver path.
* Important storage path: +1. qla2xxx is a storage fabric driver, and failures can affect host storage availability.
* Rare AND difficult-to-reach subsystem/configuration: -1. Exposure requires qla2xxx hardware and a relevant FC/NVMe fabric scenario.
* Constrained primitive: -1. The patch shows wrong deallocation of a driver object, but not an attacker-controlled arbitrary write or controlled reclaim primitive.

Paranoid additional interpretation:

* Weak LPE concern: +1. Invalid free of a pooled object can become exploitable if allocation reuse or pool state manipulation is controllable, though this is not demonstrated.
* Confidentiality impact plausible: +1. Kernel memory corruption in a storage driver can theoretically corrupt objects in ways that later expose data.
* Integrity impact plausible: +1. Wrong allocator release can corrupt kernel heap or driver pool state.
* Availability impact realistic: +1. The error path can plausibly cause system-wide storage failure or kernel panic.

## 3. Reachability analysis

The bug is not Internet remote and is not a generic local unprivileged syscall issue. Triggering depends on qla2xxx hardware, FC/NVMe support, firmware behavior, and reaching the PURLS IOCB processing path. A fabric peer or storage environment influence may be enough to shape the request path without a local host account, but practical exploitability is hardware and deployment dependent. Containers and namespaces generally do not lower privileges here because the vulnerable input comes through the physical or virtualized storage fabric and driver stack.

## 4. Severity interpretation

This is more serious than an ordinary Moderate driver crash because the primitive is an invalid free of a pooled kernel object. Conservative handling is Actionable Moderate because exposure is specialized and the corruption primitive is not shown to be controllable. Paranoid handling reaches Strong Important candidate because this is real memory corruption in a trusted storage driver path with plausible DoS and possible corruption-based confidentiality or integrity impact.

## 5. One-sentence report phrase

An invalid free in qla2xxx PURLS IOCB error handling can pass a preallocated purex pool item to `kfree()`, potentially corrupting kernel memory in a trusted FC/NVMe storage driver path.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: confirmed invalid free memory corruption in a storage driver path, with specialized but externally influenced reachability and plausible impact beyond a simple DoS.

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

Patch: scsi: qla2xxx: Fix improper freeing of purex item [ Upstream
Commit: 8e9f0a0717ba31d5842721627ade1e62d7aec012
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8e9f0a0717ba31d5842721627ade1e62d7aec012

Changed files:
  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=8e9f0a0717ba31d5842721627ade1e62d7aec012

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

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

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

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

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