CVE-2026-89848

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: 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: Quiesce response IRQ before freeing request queue

qla2xxx_delete_qpair() deletes the request queue before the response queue. qla25xx_delete_req_que() frees the request queue memory (kfree(req) in qla25xx_free_req_que()), but the response-queue MSI-X is only released later, in qla25xx_free_rsp_que(). In that window the response interrupt can still fire, qla2xxx_msix_rsp_q() queues qpair->q_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free.

The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req.

Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
41
EG Risk 41/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
Severity81% × 45%
Exploitation1% × 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.6%
EPSS %ILE
44th
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 16, 2026

Last Modified

September 16, 2026

Advisory Details (5)

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

scsi: qla2xxx: Quiesce response IRQ before freeing request queue - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Quiesce response IRQ before freeing request queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/505753ec2594c6af09a601f0dd60be7d840c1d2d
generic

scsi: qla2xxx: Quiesce response IRQ before freeing request queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/157ca7d1af45f87aa14a286754f19c3f72386988
generic

scsi: qla2xxx: Quiesce response IRQ before freeing request queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1486cc18be3e2b4c2a730f4a1b0448d009381b3d
generic

scsi: qla2xxx: Quiesce response IRQ before freeing request queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10e9f05f7fd0a103886a867ec8afe621fe4b906a

Vendor Advisories for CVE-2026-89848(1)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 26× in last 7d / 77× 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 07:44 UTCEG score recompute
  2. 2026-10-05 07:44 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 19:06 UTCGHSA enrichment
  5. 2026-10-04 06:03 UTCGHSA enrichment
  6. 2026-10-03 17:25 UTCEG score recompute
  7. 2026-10-03 17:25 UTCGHSA enrichment
  8. 2026-10-03 04:47 UTCEG score recompute
  9. 2026-10-03 04:47 UTCGHSA enrichment
  10. 2026-10-02 16:08 UTCGHSA enrichment
  11. 2026-10-02 03:30 UTCEG score recompute
  12. 2026-10-02 03:30 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 14:52 UTCGHSA enrichment
  15. 2026-10-01 02:14 UTCEG score recompute
  16. 2026-10-01 02:14 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 13:37 UTCGHSA enrichment
  19. 2026-09-30 00:55 UTCEG score recompute
  20. 2026-09-30 00:55 UTCGHSA enrichment
  21. 2026-09-29 08:32 UTCEG score recompute
  22. 2026-09-29 08:32 UTCGHSA enrichment
  23. 2026-09-28 19:54 UTCEG score recompute
  24. 2026-09-28 19:54 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 52 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 07:14 UTCGHSA enrichment
  3. 2026-09-27 18:36 UTCEG score recompute
  4. 2026-09-27 18:36 UTCGHSA enrichment
  5. 2026-09-27 13:49 UTCEPSS rescore
  6. 2026-09-27 05:58 UTCGHSA enrichment
  7. 2026-09-26 17:19 UTCEG score recompute
  8. 2026-09-26 17:19 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 04:41 UTCEG score recompute
  11. 2026-09-26 04:41 UTCGHSA enrichment
  12. 2026-09-25 15:51 UTCGHSA enrichment
  13. 2026-09-25 03:13 UTCGHSA enrichment
  14. 2026-09-24 14:35 UTCEG score recompute
  15. 2026-09-24 14:35 UTCGHSA enrichment
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-24 01:55 UTCEG score recompute
  18. 2026-09-24 01:55 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 13:17 UTCGHSA enrichment
  21. 2026-09-23 00:39 UTCEG score recompute
  22. 2026-09-23 00:39 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 12:01 UTCGHSA enrichment
  25. 2026-09-21 23:23 UTCEG score recompute
  26. 2026-09-21 23:23 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 10:45 UTCGHSA enrichment
  29. 2026-09-20 22:07 UTCEG score recompute
  30. 2026-09-20 22:07 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 09:29 UTCGHSA enrichment
  33. 2026-09-19 20:51 UTCEG score recompute
  34. 2026-09-19 20:51 UTCGHSA enrichment
  35. 2026-09-19 08:13 UTCGHSA enrichment
  36. 2026-09-18 19:36 UTCEG score recompute
  37. 2026-09-18 19:36 UTCGHSA enrichment
  38. 2026-09-18 19:28 UTCEPSS rescore
  39. 2026-09-18 06:58 UTCEG score recompute
  40. 2026-09-18 06:58 UTCGHSA enrichment
  41. 2026-09-17 19:32 UTCEPSS rescore
  42. 2026-09-17 18:20 UTCGHSA enrichment
  43. 2026-09-17 04:02 UTCEG score recompute
  44. 2026-09-17 04:02 UTCGHSA enrichment
  45. 2026-09-16 15:24 UTCEG score recompute
  46. 2026-09-16 15:24 UTCGHSA enrichment
  47. 2026-09-16 14:49 UTCEG score recompute▲ 8.10
  48. 2026-09-16 14:49 UTCGHSA enrichment
  49. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  50. 2026-09-16 11:21 UTCNVD update
  51. 2026-09-16 10:40 UTCEG score recompute
  52. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89848?
CVE-2026-89848 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Quiesce response IRQ before freeing request queue qla2xxxdeleteqpair() deletes the request queue before the response queue. qla25xxdeletereq_que() frees the request queue memory (kfree(req) in qla25xxfreereq_que()),…
When was CVE-2026-89848 disclosed?
CVE-2026-89848 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89848 actively exploited?
CVE-2026-89848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89848?
CVE-2026-89848 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89848?
No fix for CVE-2026-89848 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-89848 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-89848

Explore →

Is Your Infrastructure Affected by CVE-2026-89848?

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