CVE-2026-89865 — scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and < a476377a66897549dd49bee319f4df66623417b7≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and < 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and < 97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and < 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and < 581590f560b74399151b3cbc88574424c2f3d2dc≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and < b157256c28086c434afd70cc78bf9b4d8caf1276≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and < a5501c42256235523c4dddf799f032dfbf4f4c77≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and < b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc and 1 moreversion 3.2 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 20, 2026 · 5 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/a476377a66897549dd49bee319f4df66623417b7
- nvd.nist.gov/vuln/detail/CVE-2026-89865
- git.kernel.org/stable/c/97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8
- git.kernel.org/stable/c/84bde5ce4038d9ad811e5c994305bbfcbd7a9f79
- git.kernel.org/stable/c/581590f560b74399151b3cbc88574424c2f3d2dc
- github.com/advisories/GHSA-rqfh-jqm9-82qm
- git.kernel.org/stable/c/b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc
- git.kernel.org/stable/c/a5501c42256235523c4dddf799f032dfbf4f4c77
- git.kernel.org/stable/c/09703bc7c0be3a7a155b0ff5f21f6765ba3f519c
- git.kernel.org/stable/c/b157256c28086c434afd70cc78bf9b4d8caf1276
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98869 bpf: Infer zext_dst based on static register liveness analysis 1h
- Unknown CVE-2023-7356 Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID 1h
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 3d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 3d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 3d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89865 is "scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.