CVE-2026-89847

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.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: Avoid double completion in async IOCB timeout

qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then call sp->done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking whether the SRB was actually found and removed.

If the response ISR completes the same handle first, it removes the SRB under qp_lock_ptr and runs sp->done() -> complete(sp->comp). The submitter qla24xx_control_vp() wakes from wait_for_completion(), clears sp->comp, drops its reference and returns, reclaiming the on-stack completion. The timer reference keeps the SRB alive across the timeout handler, but not the submitter's stack. The timeout then issues a second sp->done() -> qla_ctrlvp_sp_done(), which evaluates "if (sp->comp) complete(sp->comp)"; with the pointer loaded before the submitter's NULL store, complete() writes into the freed stack frame, a use-after-free.

Track whether this path removed the SRB from outstanding_cmds and only call sp->done() when it did, so the command is completed exactly once by whichever path owns it. This mirrors the sp_found guard already used in qla24xx_abort_iocb_timeout().

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
49
EG Risk 49/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
Severity98% × 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.7%
EPSS %ILE
52nd
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 total (CVSS ≥ 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 (8)

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

scsi: qla2xxx: Avoid double completion in async IOCB timeout - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Avoid double completion in async IOCB timeout - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Avoid double completion in async IOCB timeout - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Avoid double completion in async IOCB timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9fa1d71233a82416492d9c9de9756ebe140fe714
generic

scsi: qla2xxx: Avoid double completion in async IOCB timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/845d4abd92cd2f97551356c8b281ad6e197acb07
generic

scsi: qla2xxx: Avoid double completion in async IOCB timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7257b5e1fb6c9387714f66e01b79ec82b717eede
generic

scsi: qla2xxx: Avoid double completion in async IOCB timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71a7b6e3c7f121439f51a058e53d4a8e05b63dec
generic

scsi: qla2xxx: Avoid double completion in async IOCB timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e217a9482eabbd8b29847be334c74cf468d3544

Vendor Advisories for CVE-2026-89847(2)

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 101× in last 7d / 276× 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.

Showing the most recent 100 of 276 total refreshes for this CVE.

  1. 2026-10-05 09:57 UTCVendor advisory
  2. 2026-10-05 09:57 UTCGHSA enrichment
  3. 2026-10-05 06:14 UTCVendor advisory
  4. 2026-10-05 06:14 UTCGHSA enrichment
  5. 2026-10-05 02:31 UTCEG score recompute
  6. 2026-10-05 02:31 UTCVendor advisory
  7. 2026-10-05 02:31 UTCGHSA enrichment
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-04 22:49 UTCVendor advisory
  10. 2026-10-04 22:49 UTCGHSA enrichment
  11. 2026-10-04 19:06 UTCVendor advisory
  12. 2026-10-04 19:06 UTCGHSA enrichment
  13. 2026-10-04 15:21 UTCVendor advisory
  14. 2026-10-04 15:21 UTCGHSA enrichment
  15. 2026-10-04 11:22 UTCVendor advisory
  16. 2026-10-04 11:22 UTCGHSA enrichment
  17. 2026-10-04 07:40 UTCVendor advisory
  18. 2026-10-04 07:40 UTCGHSA enrichment
  19. 2026-10-04 03:58 UTCVendor advisory
  20. 2026-10-04 03:58 UTCGHSA enrichment
  21. 2026-10-04 00:13 UTCVendor advisory
  22. 2026-10-04 00:13 UTCGHSA enrichment
  23. 2026-10-03 20:30 UTCVendor advisory
  24. 2026-10-03 20:30 UTCGHSA enrichment
  25. 2026-10-03 16:48 UTCEG score recompute
Show 75 more
  1. 2026-10-03 16:48 UTCVendor advisory
  2. 2026-10-03 16:47 UTCGHSA enrichment
  3. 2026-10-03 13:05 UTCVendor advisory
  4. 2026-10-03 13:05 UTCGHSA enrichment
  5. 2026-10-03 09:19 UTCVendor advisory
  6. 2026-10-03 09:19 UTCGHSA enrichment
  7. 2026-10-03 05:29 UTCVendor advisory
  8. 2026-10-03 05:29 UTCGHSA enrichment
  9. 2026-10-03 01:46 UTCVendor advisory
  10. 2026-10-03 01:46 UTCGHSA enrichment
  11. 2026-10-02 22:03 UTCVendor advisory
  12. 2026-10-02 22:03 UTCGHSA enrichment
  13. 2026-10-02 18:20 UTCEG score recompute
  14. 2026-10-02 18:20 UTCVendor advisory
  15. 2026-10-02 18:20 UTCGHSA enrichment
  16. 2026-10-02 14:38 UTCVendor advisory
  17. 2026-10-02 14:38 UTCGHSA enrichment
  18. 2026-10-02 10:52 UTCVendor advisory
  19. 2026-10-02 10:52 UTCGHSA enrichment
  20. 2026-10-02 06:54 UTCVendor advisory
  21. 2026-10-02 06:54 UTCGHSA enrichment
  22. 2026-10-02 03:12 UTCVendor advisory
  23. 2026-10-02 03:12 UTCGHSA enrichment
  24. 2026-10-01 23:01 UTCEG score recompute
  25. 2026-10-01 23:01 UTCVendor advisory
  26. 2026-10-01 23:01 UTCGHSA enrichment
  27. 2026-10-01 19:51 UTCEPSS rescore
  28. 2026-10-01 19:17 UTCVendor advisory
  29. 2026-10-01 19:17 UTCGHSA enrichment
  30. 2026-10-01 15:34 UTCVendor advisory
  31. 2026-10-01 15:34 UTCGHSA enrichment
  32. 2026-10-01 11:49 UTCVendor advisory
  33. 2026-10-01 11:49 UTCGHSA enrichment
  34. 2026-10-01 08:04 UTCVendor advisory
  35. 2026-10-01 08:04 UTCGHSA enrichment
  36. 2026-10-01 04:22 UTCVendor advisory
  37. 2026-10-01 04:22 UTCGHSA enrichment
  38. 2026-10-01 00:39 UTCVendor advisory
  39. 2026-10-01 00:39 UTCGHSA enrichment
  40. 2026-09-30 20:40 UTCVendor advisory
  41. 2026-09-30 20:40 UTCGHSA enrichment
  42. 2026-09-30 16:58 UTCEG score recompute
  43. 2026-09-30 16:58 UTCVendor advisory
  44. 2026-09-30 16:58 UTCGHSA enrichment
  45. 2026-09-30 15:04 UTCEPSS rescore
  46. 2026-09-30 12:12 UTCVendor advisory
  47. 2026-09-30 12:12 UTCGHSA enrichment
  48. 2026-09-30 08:29 UTCVendor advisory
  49. 2026-09-30 08:29 UTCGHSA enrichment
  50. 2026-09-30 04:46 UTCVendor advisory
  51. 2026-09-30 04:46 UTCGHSA enrichment
  52. 2026-09-30 00:55 UTCVendor advisory
  53. 2026-09-30 00:55 UTCGHSA enrichment
  54. 2026-09-29 18:45 UTCEG score recompute
  55. 2026-09-29 18:45 UTCVendor advisory
  56. 2026-09-29 18:44 UTCGHSA enrichment
  57. 2026-09-29 14:30 UTCVendor advisory
  58. 2026-09-29 14:30 UTCGHSA enrichment
  59. 2026-09-29 10:45 UTCVendor advisory
  60. 2026-09-29 10:45 UTCGHSA enrichment
  61. 2026-09-29 06:48 UTCVendor advisory
  62. 2026-09-29 06:48 UTCGHSA enrichment
  63. 2026-09-29 03:06 UTCVendor advisory
  64. 2026-09-29 03:06 UTCGHSA enrichment
  65. 2026-09-28 23:23 UTCEG score recompute
  66. 2026-09-28 23:23 UTCVendor advisory
  67. 2026-09-28 23:23 UTCGHSA enrichment
  68. 2026-09-28 19:41 UTCVendor advisory
  69. 2026-09-28 19:41 UTCGHSA enrichment
  70. 2026-09-28 15:49 UTCEG score recompute
  71. 2026-09-28 15:49 UTCVendor advisory
  72. 2026-09-28 15:49 UTCGHSA enrichment
  73. 2026-09-28 13:52 UTCEPSS rescore
  74. 2026-09-28 13:52 UTCEPSS rescore
  75. 2026-09-28 12:06 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-89847?
CVE-2026-89847 is a critical vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid double completion in async IOCB timeout qla2x00asynciocb_timeout() tries to abort a timed-out async IOCB. When qla24xxasyncabortcmd() fails, both the SRBLOGIN_CMD path and the SRBCTRLVP/default path scan…
When was CVE-2026-89847 disclosed?
CVE-2026-89847 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-89847 actively exploited?
CVE-2026-89847 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89847?
CVE-2026-89847 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89847?
No fix for CVE-2026-89847 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-89847 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-89847

Explore →

Is Your Infrastructure Affected by CVE-2026-89847?

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