CVE-2026-97528

Description

A flaw was found in the Linux kernel's qla2xxx driver. This vulnerability allows an attacker on the storage network to cause a Denial of Service (DoS) or memory corruption. When an error occurs during the handling of Non-Volatile Memory Express (NVMe) Link Service responses, the driver releases an internal context structure without unlinking it from an active tracking list. Subsequent list operations access or modify this freed memory, potentially resulting in a system crash.

Statement

A use-after-free can occur in the qla2xxx NVMe over Fibre Channel unsolicited LS response path because qla_nvme_xmt_ls_rsp frees an unsolicited context while it is still linked in fcport unsol_ctx_head. A later list_add_tail or list_del operation for the same FC port can dereference the freed list node, corrupt kernel list metadata, and cause a kernel crash. The issue requires a specific error path during LS response transmission and subsequent list activity, so AC:H is appropriate. For the CVSS the PR:N because an attacker with access to the relevant Fibre Channel fabric does not need local privileges on the target host. AV:A is used because NVMe over Fibre Channel is normally reachable only from an attached or trusted SAN participant and is not generally exposed to the public Internet. Impact is at least denial of service through kernel memory corruption. In the worst case the stale list write may provide confidentiality or integrity impact and should be reviewed manually.

Mitigation

Prevent the qla2xxx kernel module from loading if QLogic Fibre Channel Host Bus Adapters (HBAs) or NVMe over Fibre Channel are not required on the system:

1. Blacklist the module by creating a configuration file:
# echo "blacklist qla2xxx" >> /etc/modprobe.d/blacklist-qla2xxx.conf

2. Prevent the module from loading through other dependencies or auto-loading:
# echo "install qla2xxx /bin/true" >> /etc/modprobe.d/blacklist-qla2xxx.conf

Caveat: Disabling this module prevents the system from using QLogic Fibre Channel adapters and attached storage. If the module is currently loaded into memory, a system restart is required for the configuration changes to take effect.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.3N/A8.8
Attack VectorAdjacent NetworkN/AAdjacent Network
Attack ComplexityHighN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.