Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae – < 8f01f886cc5e7bbc16cbf1a9928fdebbc911e973
    • affected 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae – < 2be39946abcde5a6416fb074ef728429e246a996
    • affected 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae – < 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e
    • affected 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae – < 9a756f277eb89f769dbf380f38245c270d31fdb5
    • affected 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae – < 32d6df14fdab71fe1ba304fd9a0db0411ea2e043
    • affected 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae – < 97ca58b0fb026799b99e3d552d5f69cf9a3113ad
    • affected 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae – < 47049fdadc0eaa115e813735b827e1379c0d2cf8
    • affected 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae – < 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89864 badge
[![CVE-2026-89864](https://cveledger.app/badge/CVE-2026-89864.svg)](https://cveledger.app/cve/CVE-2026-89864)

Record last updated .