CVE-2026-97527

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock

The fcport->unsol_ctx_head list is modified from several contexts without a common lock. Entries are added in qla2xxx_process_purls_iocb() from the response queue ISR (under the qpair qp_lock), while they are removed from qla2xxx_process_purls_pkt() (DPC/purex worker), qla_nvme_xmt_ls_rsp() (NVMe-FC transport callback) and qla_nvme_release_lsrsp_cmd_kref() (SRB completion). The qpair qp_lock cannot serialize this per-fcport list since multiqueue adapters add entries through different qpairs, so a concurrent add and delete (or two concurrent deletes) can corrupt the list pointers.

Introduce a dedicated per-fcport spinlock, unsol_ctx_lock, initialized in qla2x00_alloc_fcport(), and take it around every list_add_tail()/list_del() on unsol_ctx_head. The add nests under the existing qp_lock; no delete path takes qp_lock, so the lock order is consistent and deadlock free.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76da0c43c63eb0496649e372ac64466364d0fe7d
generic

scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d8ad6bc8cc5eff1870cef00a0d611f38f8b6bd0
generic

scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b211d138cad86f749826d6132db6388eded992d8

Vendor Advisories for CVE-2026-97527(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 46× in last 7d / 64× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 08:27 UTCEG score recompute
  2. 2026-10-05 08:27 UTCVendor advisory
  3. 2026-10-05 08:27 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 21:13 UTCVendor advisory
  6. 2026-10-04 21:13 UTCGHSA enrichment
  7. 2026-10-04 09:57 UTCVendor advisory
  8. 2026-10-04 09:57 UTCGHSA enrichment
  9. 2026-10-03 22:44 UTCEG score recompute
  10. 2026-10-03 22:44 UTCVendor advisory
  11. 2026-10-03 22:44 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 11:30 UTCVendor advisory
  14. 2026-10-03 11:30 UTCGHSA enrichment
  15. 2026-10-03 06:24 UTCVendor advisory
  16. 2026-10-03 06:24 UTCGHSA enrichment
  17. 2026-10-02 19:11 UTCEG score recompute
  18. 2026-10-02 19:11 UTCVendor advisory
  19. 2026-10-02 19:11 UTCGHSA enrichment
  20. 2026-10-02 17:57 UTCEPSS rescore
  21. 2026-10-02 07:57 UTCVendor advisory
  22. 2026-10-02 07:57 UTCGHSA enrichment
  23. 2026-10-01 20:44 UTCEG score recompute
  24. 2026-10-01 20:44 UTCVendor advisory
  25. 2026-10-01 20:44 UTCGHSA enrichment
Show 39 more
  1. 2026-10-01 19:51 UTCEPSS rescore
  2. 2026-10-01 09:30 UTCVendor advisory
  3. 2026-10-01 09:30 UTCGHSA enrichment
  4. 2026-09-30 22:17 UTCEG score recompute
  5. 2026-09-30 22:17 UTCVendor advisory
  6. 2026-09-30 22:17 UTCGHSA enrichment
  7. 2026-09-30 15:04 UTCEPSS rescore
  8. 2026-09-30 11:04 UTCVendor advisory
  9. 2026-09-30 11:04 UTCGHSA enrichment
  10. 2026-09-29 23:50 UTCEG score recompute
  11. 2026-09-29 23:50 UTCVendor advisory
  12. 2026-09-29 23:50 UTCGHSA enrichment
  13. 2026-09-29 09:24 UTCVendor advisory
  14. 2026-09-29 09:24 UTCGHSA enrichment
  15. 2026-09-28 22:11 UTCEG score recompute
  16. 2026-09-28 22:11 UTCVendor advisory
  17. 2026-09-28 22:11 UTCGHSA enrichment
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 10:52 UTCVendor advisory
  21. 2026-09-28 10:52 UTCGHSA enrichment
  22. 2026-09-27 23:39 UTCEG score recompute
  23. 2026-09-27 23:39 UTCGHSA enrichment
  24. 2026-09-27 13:49 UTCEPSS rescore
  25. 2026-09-27 12:24 UTCGHSA enrichment
  26. 2026-09-27 01:10 UTCEG score recompute
  27. 2026-09-27 01:10 UTCGHSA enrichment
  28. 2026-09-26 15:59 UTCEPSS rescore
  29. 2026-09-26 13:55 UTCGHSA enrichment
  30. 2026-09-26 02:39 UTCEG score recompute
  31. 2026-09-26 02:39 UTCGHSA enrichment
  32. 2026-09-25 15:26 UTCEG score recompute
  33. 2026-09-25 15:26 UTCGHSA enrichment
  34. 2026-09-25 14:53 UTCEG score recompute▲ 8.80
  35. 2026-09-25 14:53 UTCGHSA enrichment
  36. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  37. 2026-09-25 11:29 UTCNVD update
  38. 2026-09-25 10:41 UTCEG score recompute
  39. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97527?
CVE-2026-97527 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock The fcport->unsolctxhead list is modified from several contexts without a common lock. Entries are added in qla2xxxprocesspurls_iocb() from the response queue ISR…
When was CVE-2026-97527 disclosed?
CVE-2026-97527 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97527 actively exploited?
CVE-2026-97527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97527?
CVE-2026-97527 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97527?
No fix for CVE-2026-97527 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97527 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97527

Explore →

Is Your Infrastructure Affected by CVE-2026-97527?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs