CVE-2026-97531

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: 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: Skip vport under deletion in report ID acquisition

qla24xx_report_id_acquisition() format-1 handling walks ha->vp_list under vport_slock, takes a vref_count on the matching vport and calls qla_update_host_map() to register its port id.

A vport teardown via qla24xx_vport_delete() sets VPORT_DELETE, then qla24xx_disable_vp() removes the vport from the host_map btree and zeroes vha->d_id (RESET_AL_PA). The vport is only unlinked from vp_list later, in qla24xx_deallocate_vp_id(), which clears vp_map[idx] (RESET_VP_IDX) but does not touch host_map. In the window in between, report ID acquisition can still find the vport on vp_list and call qla_update_host_map(); with d_id already zeroed it takes the btree_insert32() path and re-inserts the dying vport into host_map. Nothing cleans that entry afterwards, so once scsi_host_put() frees the vha a later host_map lookup dereferences freed memory.

Skip a vport that has VPORT_DELETE set before taking the reference, so it is neither re-registered nor scheduled for DPC re-registration. This mirrors the existing guard in qla2x00_alert_all_vps().

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
38
EG Risk 38/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
Severity75% × 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
18th
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: Skip vport under deletion in report ID acquisition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23582731afa35031c94fadb71a4f3b4afd094649
generic

scsi: qla2xxx: Skip vport under deletion in report ID acquisition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a83979d92782f83c90888ebe19bdc9420521940
generic

scsi: qla2xxx: Skip vport under deletion in report ID acquisition - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-97531(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
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 43× in last 7d / 61× 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-04 23:37 UTCEG score recompute
  2. 2026-10-04 23:37 UTCVendor advisory
  3. 2026-10-04 23:36 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 11:34 UTCVendor advisory
  6. 2026-10-04 11:34 UTCGHSA enrichment
  7. 2026-10-03 23:32 UTCEG score recompute
  8. 2026-10-03 23:32 UTCVendor advisory
  9. 2026-10-03 23:32 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 11:30 UTCVendor advisory
  12. 2026-10-03 11:30 UTCGHSA enrichment
  13. 2026-10-03 05:09 UTCEG score recompute
  14. 2026-10-03 05:09 UTCVendor advisory
  15. 2026-10-03 05:09 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 17:07 UTCVendor advisory
  18. 2026-10-02 17:07 UTCGHSA enrichment
  19. 2026-10-02 05:04 UTCEG score recompute
  20. 2026-10-02 05:04 UTCVendor advisory
  21. 2026-10-02 05:03 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 17:01 UTCVendor advisory
  24. 2026-10-01 17:01 UTCGHSA enrichment
  25. 2026-10-01 04:42 UTCVendor advisory
Show 36 more
  1. 2026-10-01 04:42 UTCGHSA enrichment
  2. 2026-09-30 16:36 UTCEG score recompute
  3. 2026-09-30 16:36 UTCVendor advisory
  4. 2026-09-30 16:36 UTCGHSA enrichment
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-30 03:56 UTCVendor advisory
  7. 2026-09-30 03:56 UTCGHSA enrichment
  8. 2026-09-29 15:54 UTCEG score recompute
  9. 2026-09-29 15:54 UTCVendor advisory
  10. 2026-09-29 15:54 UTCGHSA enrichment
  11. 2026-09-29 03:52 UTCEG score recompute
  12. 2026-09-29 03:52 UTCVendor advisory
  13. 2026-09-29 03:52 UTCGHSA enrichment
  14. 2026-09-28 15:49 UTCEG score recompute
  15. 2026-09-28 15:49 UTCVendor advisory
  16. 2026-09-28 15:49 UTCGHSA enrichment
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 03:46 UTCGHSA enrichment
  20. 2026-09-27 15:44 UTCEG score recompute
  21. 2026-09-27 15:43 UTCGHSA enrichment
  22. 2026-09-27 13:49 UTCEPSS rescore
  23. 2026-09-27 03:40 UTCEG score recompute
  24. 2026-09-27 03:40 UTCGHSA enrichment
  25. 2026-09-26 15:59 UTCEPSS rescore
  26. 2026-09-26 15:35 UTCGHSA enrichment
  27. 2026-09-26 03:33 UTCEG score recompute
  28. 2026-09-26 03:32 UTCGHSA enrichment
  29. 2026-09-25 15:26 UTCEG score recompute
  30. 2026-09-25 15:26 UTCGHSA enrichment
  31. 2026-09-25 14:53 UTCEG score recompute▲ 7.50
  32. 2026-09-25 14:53 UTCGHSA enrichment
  33. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  34. 2026-09-25 11:29 UTCNVD update
  35. 2026-09-25 10:41 UTCEG score recompute
  36. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97531?
CVE-2026-97531 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Skip vport under deletion in report ID acquisition qla24xxreportidacquisition() format-1 handling walks ha->vplist under vportslock, takes a vrefcount on the matching vport and calls qlaupdatehost_map() to register…
When was CVE-2026-97531 disclosed?
CVE-2026-97531 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-97531 actively exploited?
CVE-2026-97531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97531?
CVE-2026-97531 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97531?
No fix for CVE-2026-97531 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-97531 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-97531

Explore →

Is Your Infrastructure Affected by CVE-2026-97531?

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

Book a Demo →Browse All CVEs