CVE-2026-89864

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: 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: Bound i2c->length in I2C bsg handlers

struct qla_i2c_access carries a 16-bit length field alongside a fixed 64-byte buffer:

struct qla_i2c_access { uint16_t device, offset, option, length; uint8_t buffer[0x40]; } __packed;

qla2x00_write_i2c() and qla2x00_read_i2c() use the user-supplied i2c->length without any bounds check. i2c is overlaid on a 256-byte on-stack buffer and sfp is a 256-byte DMA-pool buffer, so a length up to 65535 overruns both:

  • write: memcpy(sfp, i2c->buffer, i2c->length) over-reads the stack and
over-writes the sfp heap buffer, and qla2x00_write_sfp() then DMAs i2c->length bytes out of the 256-byte buffer.
  • read: qla2x00_read_sfp() DMAs i2c->length bytes into the 256-byte sfp,
then memcpy(i2c->buffer, sfp, i2c->length) overflows the 64-byte buffer inside the on-stack array.

A caller holding CAP_SYS_RAWIO can use this to corrupt the heap and the kernel stack. Reject requests whose length exceeds the buffer before any copy or DMA transfer in both handlers.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

References (8)

Vendor Advisories for CVE-2026-89864(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 10× in last 7d / 31× 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:22 UTCEPSS rescore
  2. 2026-10-02 22:34 UTCVendor advisory
  3. 2026-10-02 22:34 UTCGHSA enrichment
  4. 2026-10-01 19:51 UTCEPSS rescore
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-30 04:46 UTCEG score recompute
  7. 2026-09-30 04:46 UTCVendor advisory
  8. 2026-09-30 04:46 UTCGHSA enrichment
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 13:49 UTCEPSS rescore
  12. 2026-09-27 10:47 UTCVendor advisory
  13. 2026-09-27 10:47 UTCGHSA enrichment
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 16:48 UTCVendor advisory
  16. 2026-09-24 16:48 UTCGHSA enrichment
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-22 16:01 UTCEPSS rescore
  20. 2026-09-21 23:01 UTCVendor advisory
  21. 2026-09-21 23:00 UTCGHSA enrichment
  22. 2026-09-21 21:09 UTCEPSS rescore
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-19 05:12 UTCEG score recompute
  25. 2026-09-19 05:12 UTCVendor advisory
Show 6 more
  1. 2026-09-19 05:12 UTCGHSA enrichment
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:32 UTCEPSS rescore
  4. 2026-09-16 11:21 UTCNVD update
  5. 2026-09-16 10:40 UTCEG score recompute
  6. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89864?
CVE-2026-89864 is a publicly disclosed vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Bound i2c->length in I2C bsg handlers struct qlai2caccess carries a 16-bit length field alongside a fixed 64-byte buffer: struct qlai2caccess { uint16_t device, offset, option, length; uint8_t buffer[0x40]; } packed;…
When was CVE-2026-89864 disclosed?
CVE-2026-89864 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-89864 actively exploited?
CVE-2026-89864 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-89864?
No fix for CVE-2026-89864 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-89864 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-89864

Explore →

Is Your Infrastructure Affected by CVE-2026-89864?

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

Book a Demo →Browse All CVEs