← All Advisories

CVE-2026-97528

Last refreshed2026-10-03

Status: UPDATED  |  Advisory ID: CVE-2026-97528

Key Details

CVECVE-2026-97528
CVSS Score / Version8.8 (High) / CVSS v3.1
Updated2026-09-25
CVSS VectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Proseattack vector is adjacent; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected productsLinux Linux

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux
SubsystemsGeneral OT
SectorsMultiple

What to Know

In the Linux kernel, the following vulnerability has been resolved:

scsi: qla2xxx: Unlink NVMe unsol ctx before freeing on LS reject error

qla_nvme_xmt_ls_rsp() obtains uctx, which was linked into

fcport->unsol_ctx_head by qla2xxx_process_purls_iocb() and is still linked

when the NVMe transport calls back to transmit the LS response. On the

error (out:) path the function frees uctx with kfree() but never removes

it from the list. This leaves a freed node in fcport->unsol_ctx_head: the

next list_add_tail() for that fcport writes through the freed node, and a

subsequent list_del() can corrupt the list or panic.

Unlink uctx with list_del() before kfree() on the error path, matching the

other free sites in qla_nvme_release_lsrsp_cmd_kref() and

qla2xxx_process_purls_pkt(). qla2x00_rel_sp() in the failure path only

returns the SRB to its pool and does not invoke sp->put_fn, so the out:

path is the sole free and uctx is always still linked there. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-97528
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-97528