CVE-2026-89864

Unknown

Description

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.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedSep 16, 2026
First seenSep 16, 2026

How to fix

Update
  • Linux Linux8f01f886cc5e7bbc16cbf1a9928fdebbc911e973, 2be39946abcde5a6416fb074ef728429e246a996, 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e, 9a756f277eb89f769dbf380f38245c270d31fdb5, 32d6df14fdab71fe1ba304fd9a0db0411ea2e043, 97ca58b0fb026799b99e3d552d5f69cf9a3113ad, 47049fdadc0eaa115e813735b827e1379c0d2cf8, 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59 or later

Affected products

ProductAffected versionsFixed in
Linux Linux9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae ≤ v < 8f01f886cc5e7bbc16cbf1a9928fdebbc911e973, 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae ≤ v < 2be39946abcde5a6416fb074ef728429e246a996, 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae ≤ v < 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e, 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae ≤ v < 9a756f277eb89f769dbf380f38245c270d31fdb5, 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae ≤ v < 32d6df14fdab71fe1ba304fd9a0db0411ea2e043, 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae ≤ v < 97ca58b0fb026799b99e3d552d5f69cf9a3113ad, 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae ≤ v < 47049fdadc0eaa115e813735b827e1379c0d2cf8, 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae ≤ v < 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59, 3.78f01f886cc5e7bbc16cbf1a9928fdebbc911e973, 2be39946abcde5a6416fb074ef728429e246a996, 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e, 9a756f277eb89f769dbf380f38245c270d31fdb5, 32d6df14fdab71fe1ba304fd9a0db0411ea2e043, 97ca58b0fb026799b99e3d552d5f69cf9a3113ad, 47049fdadc0eaa115e813735b827e1379c0d2cf8, 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.