CVE-2026-97536

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: Fix use-after-free of qpair work on queue teardown

The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock.

During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair. free_irq() waits for running hardirq handlers but does not cancel work already placed on ha->wq. A still-pending q_work then runs qla_do_work() against the freed qpair and response queue, causing a use-after-free. This is especially likely during full adapter teardown, where destroy_workqueue(ha->wq) forces pending work to run after the queue pairs have been freed.

Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que() after free_irq() has released the interrupt (so no new work can be queued) and before the response queue and qpair memory are freed (so the flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq to match the INIT_WORK() condition and avoid operating on an uninitialized work_struct.

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
17th
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: Fix use-after-free of qpair work on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19788a55cab61d78e33e0914a5a31d27843e8a4a
generic

scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f1f4d1cb93eeeb250eac9405121933e268eefbd3
generic

scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1710a69fd74d0b4bdfcc57c3309b1c4057f70d85

Vendor Advisories for CVE-2026-97536(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:23 UTCEPSS rescore
  2. 2026-10-04 22:24 UTCVendor advisory
  3. 2026-10-04 22:24 UTCGHSA enrichment
  4. 2026-10-04 10:49 UTCVendor advisory
  5. 2026-10-04 10:48 UTCGHSA enrichment
  6. 2026-10-03 23:11 UTCEG score recompute
  7. 2026-10-03 23:11 UTCVendor advisory
  8. 2026-10-03 23:11 UTCGHSA enrichment
  9. 2026-10-03 14:26 UTCEPSS rescore
  10. 2026-10-03 11:29 UTCVendor advisory
  11. 2026-10-03 11:29 UTCGHSA enrichment
  12. 2026-10-03 09:06 UTCVendor advisory
  13. 2026-10-03 09:06 UTCGHSA enrichment
  14. 2026-10-02 21:28 UTCEG score recompute
  15. 2026-10-02 21:28 UTCVendor advisory
  16. 2026-10-02 21:28 UTCGHSA enrichment
  17. 2026-10-02 17:57 UTCEPSS rescore
  18. 2026-10-02 09:48 UTCVendor advisory
  19. 2026-10-02 09:48 UTCGHSA enrichment
  20. 2026-10-01 22:13 UTCEG score recompute
  21. 2026-10-01 22:13 UTCVendor advisory
  22. 2026-10-01 22:13 UTCGHSA enrichment
  23. 2026-10-01 19:51 UTCEPSS rescore
  24. 2026-10-01 10:38 UTCVendor advisory
  25. 2026-10-01 10:38 UTCGHSA enrichment
Show 36 more
  1. 2026-09-30 23:00 UTCEG score recompute
  2. 2026-09-30 23:00 UTCVendor advisory
  3. 2026-09-30 23:00 UTCGHSA enrichment
  4. 2026-09-30 15:04 UTCEPSS rescore
  5. 2026-09-30 11:26 UTCVendor advisory
  6. 2026-09-30 11:26 UTCGHSA enrichment
  7. 2026-09-29 23:50 UTCEG score recompute
  8. 2026-09-29 23:50 UTCVendor advisory
  9. 2026-09-29 23:50 UTCGHSA enrichment
  10. 2026-09-29 12:09 UTCVendor advisory
  11. 2026-09-29 12:09 UTCGHSA enrichment
  12. 2026-09-29 00:34 UTCEG score recompute
  13. 2026-09-29 00:34 UTCVendor advisory
  14. 2026-09-29 00:34 UTCGHSA enrichment
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 12:59 UTCVendor advisory
  18. 2026-09-28 12:59 UTCGHSA enrichment
  19. 2026-09-28 01:24 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEG score recompute
  21. 2026-09-27 13:49 UTCGHSA enrichment
  22. 2026-09-27 13:49 UTCEPSS rescore
  23. 2026-09-27 02:12 UTCEG score recompute
  24. 2026-09-27 02:12 UTCGHSA enrichment
  25. 2026-09-26 15:59 UTCEPSS rescore
  26. 2026-09-26 14:37 UTCGHSA enrichment
  27. 2026-09-26 03:02 UTCEG score recompute
  28. 2026-09-26 03:02 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:52 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-97536?
CVE-2026-97536 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown The response queue MSI-X handler qla2xxxmsixrsp_q() schedules qladowork() via queuework(ha->wq, &qpair->qwork). qladowork() dereferences the qpair (vha, rsp) and…
When was CVE-2026-97536 disclosed?
CVE-2026-97536 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-97536 actively exploited?
CVE-2026-97536 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97536?
CVE-2026-97536 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-97536?
No fix for CVE-2026-97536 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-97536 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-97536

Explore →

Is Your Infrastructure Affected by CVE-2026-97536?

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

Book a Demo →Browse All CVEs