CVE-2026-89865: scsi: qla2xxx: Zero SFP DMA buffer in FRU/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 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c, 581590f560b74399151b3cbc88574424c2f3d2dc, 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79; 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 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c, 581590f560b74399151b3cbc88574424c2f3d2dc, 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79; 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: Zero SFP DMA buffer in FRU/I2C bsg handlers The FRU and I2C bsg handlers stage their transfer in a DMA_POOL_SIZE (256-byte) bounce buffer obtained from dma_pool_alloc(), which does not zero the allocation. They initialize only a few leading bytes before handing the buffer to qla2x00_write_sfp(). qla2x00_write_sfp() can override the transfer length with a user-supplied value: if (len == 1) opt |= BIT_0; if (opt & BIT_0) len = *sfp; *sfp is the first byte of the (user-controlled) payload, so len can grow up to 255. The device then DMA-reads len bytes from the 256-byte pool buffer. Since only a small prefix was written (e.g. MAX_FRU_SIZE == 36 bytes for a FRU version, one byte for a FRU status register), the hardware reads past the initialized region and writes up to ~219 bytes of stale DMA-pool heap memory to the device flash. Allocate the buffer with dma_pool_zalloc() in all five FRU/I2C handlers so any bytes beyond the initialized data are zero rather than stale heap contents.
- 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.2affected
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before a476377a66897549dd49bee319f4df66623417b7affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 09703bc7c0be3a7a155b0ff5f21f6765ba3f519caffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 581590f560b74399151b3cbc88574424c2f3d2dcaffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before b157256c28086c434afd70cc78bf9b4d8caf1276affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before a5501c42256235523c4dddf799f032dfbf4f4c77affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before b47d4a1547d9ef21b2e9d1a739fe2204d4be05dcaffected · git
- before 3.2not 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-89863Sep 16, 2026 · scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check30Monitor
- ← EarlierCVE-2026-89864Sep 16, 2026 · scsi: qla2xxx: Bound i2c->length in I2C bsg handlers0Monitor
- Later →CVE-2026-89866Sep 16, 2026 · media: chips-media: wave5: Resume device before setting EOS flag0Monitor
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 | 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c | Vendor (CNA) |
| Linux Linux | 581590f560b74399151b3cbc88574424c2f3d2dc | Vendor (CNA) |
| Linux Linux | 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79 | Vendor (CNA) |
| Linux Linux | 97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8 | Vendor (CNA) |
| Linux Linux | a476377a66897549dd49bee319f4df66623417b7 | Vendor (CNA) |
| Linux Linux | a5501c42256235523c4dddf799f032dfbf4f4c77 | Vendor (CNA) |
| Linux Linux | b157256c28086c434afd70cc78bf9b4d8caf1276 | Vendor (CNA) |
| Linux Linux | b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc | 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/581590f560b74399151b3cbc88574424c2f3d2dc
- git.kernel.org/stable/c/84bde5ce4038d9ad811e5c994305bbfcbd7a9f79
- git.kernel.org/stable/c/97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8
- git.kernel.org/stable/c/a476377a66897549dd49bee319f4df66623417b7
- git.kernel.org/stable/c/a5501c42256235523c4dddf799f032dfbf4f4c77
- git.kernel.org/stable/c/b157256c28086c434afd70cc78bf9b4d8caf1276
- git.kernel.org/stable/c/b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc
Vendor advisories and official records. Exploit/PoC links are deliberately left out.