Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97528scsi: qla2xxx: Unlink NVMe unsol ctx before freeing on LS reject error

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 26 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-97528, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.34% · top 72% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 875386b98857822b77ac7f95bdf367b70af5b78c – < 925a9129a514b7c3bc0a8af01e51868adbb9a83e
    • affected 875386b98857822b77ac7f95bdf367b70af5b78c – < cbbf1484496aac86038e67ac984949af58009d4b
    • affected 875386b98857822b77ac7f95bdf367b70af5b78c – < a95fc5f1c12bba1dbff72bd2611e7fad0758831b
    • affected 875386b98857822b77ac7f95bdf367b70af5b78c – < c55d649a6cc246c3ccd5d118faea230c46b60f35
    • affected 875386b98857822b77ac7f95bdf367b70af5b78c – < e46160a5d4fa59bf4d5f3412b6b5cb79edb967dd
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97528 badge
[![CVE-2026-97528](https://cveledger.app/badge/CVE-2026-97528.svg)](https://cveledger.app/cve/CVE-2026-97528)

Record last updated .