CVE-2026-89856

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: 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: Clamp MSI-X derived queue counts to avoid truncation

ha->msix_count is u16, but ha->max_req_queues, ha->max_rsp_queues and ha->max_qpairs are u8. Deriving the queue count as "ha->max_req_queues = ha->msix_count - 1" therefore truncates: a board (or a misconfigured/malicious hot-plugged device) advertising 257 MSI-X vectors yields msix_count - 1 == 256, which truncates to 0. An MSI-X count of 1 zeroes it as well, and in target mode the subsequent "ha->max_req_queues--" then underflows 0 to 255.

When the count is 0, qla2x00_alloc_queues() calls kzalloc_objs(struct req_que *, 0), which returns ZERO_SIZE_PTR. That is not NULL, so the allocation check passes and the following "ha->req_q_map[0] = req" dereferences ZERO_SIZE_PTR, corrupting memory or crashing the kernel.

Add qla_calc_queue_count() to clamp the derived value into [1, QLA_MAX_QUEUES - 1] so it always fits in u8 and is never zero, and use it at all three derivation sites (qla25xx_iospace_config(), qla83xx_iospace_config() and qla24xx_enable_msix()). Also guard the target-mode decrement so it cannot reintroduce a zero (which would in turn underflow max_qpairs).

CVSS v3
8.4
EG Score
8.4HIGHhigh confidence
EG Risk
42
EG Risk 42/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
Severity84% × 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.2%
EPSS %ILE
8th
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 (8)

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

scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33c77254e6e91f37c72c7fad4051777452b10de8
generic

scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2efe50b2da829909023de4a2eb87badb7cfa53cc
generic

scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/802068b9b683b8008fcccbf6e9ad133e597ec87c
generic

scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-89856(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 40× in last 7d / 112× 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 112 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89856?
CVE-2026-89856 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation ha->msixcount is u16, but ha->maxreqqueues, ha->maxrsp_queues and ha->max_qpairs are u8. Deriving the queue count as "ha->maxreqqueues = ha->msix_count - 1"…
When was CVE-2026-89856 disclosed?
CVE-2026-89856 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-89856 actively exploited?
CVE-2026-89856 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89856?
CVE-2026-89856 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89856?
No fix for CVE-2026-89856 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-89856 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-89856

Explore →

Is Your Infrastructure Affected by CVE-2026-89856?

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