CVE-2026-89864: scsi: qla2xxx: Bound i2c->length in I2C bsg handlers
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59, 2be39946abcde5a6416fb074ef728429e246a996, 32d6df14fdab71fe1ba304fd9a0db0411ea2e043; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59, 2be39946abcde5a6416fb074ef728429e246a996, 32d6df14fdab71fe1ba304fd9a0db0411ea2e043; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.7affected
- 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and later · before 8f01f886cc5e7bbc16cbf1a9928fdebbc911e973affected · git
- 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and later · before 2be39946abcde5a6416fb074ef728429e246a996affected · git
- 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and later · before 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0eaffected · git
- 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and later · before 9a756f277eb89f769dbf380f38245c270d31fdb5affected · git
- 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and later · before 32d6df14fdab71fe1ba304fd9a0db0411ea2e043affected · git
- 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and later · before 97ca58b0fb026799b99e3d552d5f69cf9a3113adaffected · git
- 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and later · before 47049fdadc0eaa115e813735b827e1379c0d2cf8affected · git
- 9ebb5d9c69f1f5721f9f6f49e501c674c1e184ae and later · before 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59affected · git
- before 3.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89862Sep 16, 2026 · scsi: qla2xxx: Fix BSG job leak on validate flash image error path0Monitor
- ← EarlierCVE-2026-89863Sep 16, 2026 · scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check30Monitor
- Later →CVE-2026-89865Sep 16, 2026 · scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0918ee2c0eeb4d7f45b82b3dc11e65c2d9b7ad59 | Vendor (CNA) |
| Linux Linux | 2be39946abcde5a6416fb074ef728429e246a996 | Vendor (CNA) |
| Linux Linux | 32d6df14fdab71fe1ba304fd9a0db0411ea2e043 | Vendor (CNA) |
| Linux Linux | 47049fdadc0eaa115e813735b827e1379c0d2cf8 | Vendor (CNA) |
| Linux Linux | 522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e | Vendor (CNA) |
| Linux Linux | 8f01f886cc5e7bbc16cbf1a9928fdebbc911e973 | Vendor (CNA) |
| Linux Linux | 97ca58b0fb026799b99e3d552d5f69cf9a3113ad | Vendor (CNA) |
| Linux Linux | 9a756f277eb89f769dbf380f38245c270d31fdb5 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2be39946abcde5a6416fb074ef728429e246a996
- git.kernel.org/stable/c/32d6df14fdab71fe1ba304fd9a0db0411ea2e043
- git.kernel.org/stable/c/47049fdadc0eaa115e813735b827e1379c0d2cf8
- git.kernel.org/stable/c/522d6dcdc645d8f97d6b4cdfd6d8eea307f3ff0e
- git.kernel.org/stable/c/8f01f886cc5e7bbc16cbf1a9928fdebbc911e973
- git.kernel.org/stable/c/97ca58b0fb026799b99e3d552d5f69cf9a3113ad
- git.kernel.org/stable/c/9a756f277eb89f769dbf380f38245c270d31fdb5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.