Unknown

CVE-2026-89864 — scsi: qla2xxx: Bound i2c->length in I2C bsg handlers

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.

Published Sep 16, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.21%

ahead of 11% of scored CVEs · Oct 20, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and < 8f01f886cc5e7bbc16cbf1a9928fdebbc911e973≥ 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and < 2be39946abcde5a6416fb074ef728429e246a996≥ 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and < 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e≥ 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and < 9a756f277eb89f769dbf380f38245c270d31fdb5≥ 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and < 32d6df14fdab71fe1ba304fd9a0db0411ea2e043≥ 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and < 97ca58b0fb026799b99e3d552d5f69cf9a3113ad≥ 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and < 47049fdadc0eaa115e813735b827e1379c0d2cf8≥ 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and < 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59 and 1 more version 3.7	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 20, 2026 · 5 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 16, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

10 on the record

git.kernel.org/stable/c/47049fdadc0eaa115e813735b827e1379c0d2cf8
NIST National Vulnerability Database
github.com/advisories/GHSA-vhpc-fmr8-vgcc
GitHub Security Advisories
git.kernel.org/stable/c/32d6df14fdab71fe1ba304fd9a0db0411ea2e043
NIST National Vulnerability Database
git.kernel.org/stable/c/2be39946abcde5a6416fb074ef728429e246a996
NIST National Vulnerability Database
git.kernel.org/stable/c/9a756f277eb89f769dbf380f38245c270d31fdb5
NIST National Vulnerability Database
git.kernel.org/stable/c/522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e
NIST National Vulnerability Database
git.kernel.org/stable/c/8f01f886cc5e7bbc16cbf1a9928fdebbc911e973
NIST National Vulnerability Database
git.kernel.org/stable/c/97ca58b0fb026799b99e3d552d5f69cf9a3113ad
NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2026-89864
GitHub Security Advisories
git.kernel.org/stable/c/0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 2d
Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 2d
Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 2d
Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 2d
Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 2d
Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-89864 is "scsi: qla2xxx: Bound i2c->length in I2C bsg handlers", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.