scsi: qla2xxx: Bound i2c->length in I2C bsg handlers
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae · fixed in 8f01f886cc5e7bbc16cbf1a9928fdebbc911e973; From 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae · fixed in 2be39946abcde5a6416fb074ef728429e246a996; From 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae · fixed in 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e; From 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae · fixed in 9a756f277eb89f769dbf380f38245c270d31fdb5; From 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae · fixed in 32d6df14fdab71fe1ba304fd9a0db0411ea2e043; From 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae · fixed in 97ca58b0fb026799b99e3d552d5f69cf9a3113ad; From 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae · fixed in 47049fdadc0eaa115e813735b827e1379c0d2cf8; From 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae · fixed in 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59
- Linux Linux
3.7
- KernelLinux
From 3.7.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5
References 8
git.kernel.org
- stable/c/8f01f886cc5e7bbc16cbf1a9928fdebbc911e973
- stable/c/2be39946abcde5a6416fb074ef728429e246a996
- stable/c/522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e
- stable/c/9a756f277eb89f769dbf380f38245c270d31fdb5
- stable/c/32d6df14fdab71fe1ba304fd9a0db0411ea2e043
- stable/c/97ca58b0fb026799b99e3d552d5f69cf9a3113ad
- stable/c/47049fdadc0eaa115e813735b827e1379c0d2cf8
- stable/c/0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59