Skip to content
Threat Brief

← All advisories

CVE-2026-97528

High 8.8No known exploitationFix available

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

Record last updated

CVSS score

8.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 28% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 875386b98857822b77ac7f95bdf367b70af5b78c before c55d649a6cc246c3ccd5d118faea230c46b60f35c55d649a6cc246c3ccd5d118faea230c46b60f35CVE Program
LinuxLinuxfrom 875386b98857822b77ac7f95bdf367b70af5b78c before e46160a5d4fa59bf4d5f3412b6b5cb79edb967dde46160a5d4fa59bf4d5f3412b6b5cb79edb967ddCVE Program
LinuxLinuxfrom 875386b98857822b77ac7f95bdf367b70af5b78c before 925a9129a514b7c3bc0a8af01e51868adbb9a83e925a9129a514b7c3bc0a8af01e51868adbb9a83eCVE Program
LinuxLinuxfrom 875386b98857822b77ac7f95bdf367b70af5b78c before cbbf1484496aac86038e67ac984949af58009d4bcbbf1484496aac86038e67ac984949af58009d4bCVE Program
LinuxLinuxfrom 875386b98857822b77ac7f95bdf367b70af5b78c before a95fc5f1c12bba1dbff72bd2611e7fad0758831ba95fc5f1c12bba1dbff72bd2611e7fad0758831bCVE Program
LinuxLinux6.6Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.159.1-1 on Azure Linux 3.0Not documented6.6.161.1-1Microsoft MSRC
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.112 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.53 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.160 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.7 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.6Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references