CVE-2026-89844

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.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: Hold vport_slock for host map update in report ID acquisition

qla24xx_report_id_acquisition() format-1 handling drops vport_slock after taking the vport reference and then calls qla_update_host_map() without the lock. That reaches qla_update_vp_map(), which mutates the ha->host_map btree via btree_insert32()/btree_update32()/btree_remove32() and is documented to require vport_slock to be held by the caller. Running it unlocked can race concurrent host_map updates and corrupt the btree.

The format-2 path in the same function already wraps its host_map update (SET_AL_PA) in vport_slock; the format-1 path is the lone outlier.

Hold vport_slock across the format-1 qla_update_host_map() call to honor the documented locking contract. The vref_count taken in the loop keeps the vport valid, so this only adds the missing host_map serialization.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/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
Severity88% × 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.4%
EPSS %ILE
31st
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: Hold vport_slock for host map update in report ID acquisition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7944039ba9cb5c3a935d17c91004e3b8649ff58e
generic

scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/776e4e8cbcf155302f430ce9793d1502e3c113a0
generic

scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ed66e2a67bbd22877008ff9aa64bd574a7fc011
generic

scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-89844(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
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 42× in last 7d / 118× 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 118 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89844?
CVE-2026-89844 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition qla24xxreportidacquisition() format-1 handling drops vportslock after taking the vport reference and then calls qlaupdatehost_map() without the lock. That…
When was CVE-2026-89844 disclosed?
CVE-2026-89844 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-89844 actively exploited?
CVE-2026-89844 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89844?
CVE-2026-89844 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89844?
No fix for CVE-2026-89844 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-89844 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-89844

Explore →

Is Your Infrastructure Affected by CVE-2026-89844?

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

Book a Demo →Browse All CVEs