CVE-2026-89864

scsi: qla2xxx: Bound i2c->length in I2C bsg handlers

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.79ebb5d9c69f1f5721f9f6f49e501c674c1e184ae
Vendor states this is fixed in 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59 (fixed)
Vendor states this is fixed in 2be39946abcde5a6416fb074ef728429e246a996 (fixed)
Vendor states this is fixed in 32d6df14fdab71fe1ba304fd9a0db0411ea2e043 (fixed)
Vendor states this is fixed in 47049fdadc0eaa115e813735b827e1379c0d2cf8 (fixed)
Vendor states this is fixed in 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e (fixed)
Vendor states this is fixed in 8f01f886cc5e7bbc16cbf1a9928fdebbc911e973 (fixed)
Vendor states this is fixed in 97ca58b0fb026799b99e3d552d5f69cf9a3113ad (fixed)
Vendor states this is fixed in 9a756f277eb89f769dbf380f38245c270d31fdb5 (fixed)
Vendor states this is fixed in 3.7 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card