CVE-2026-89858: scsi: qla2xxx: Bound image count in qla2x00_update_fru_versions()
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 047f1f7ee6f85bde28abfdda9fa550191ddc0532, 7b22b4cb8822805cef7ba618da6f76e1474d68bd, 7e3154c97ec15460f715dbbe4097c255cce110b1; 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 047f1f7ee6f85bde28abfdda9fa550191ddc0532, 7b22b4cb8822805cef7ba618da6f76e1474d68bd, 7e3154c97ec15460f715dbbe4097c255cce110b1; 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 image count in qla2x00_update_fru_versions() qla2x00_update_fru_versions() copies the user-supplied BSG request into a fixed 256-byte stack buffer (bsg[DMA_POOL_SIZE]) and then iterates list->count times over the qla_image_version array embedded in that buffer, advancing the image pointer each iteration. count is taken directly from user input with no upper bound, while only (DMA_POOL_SIZE - sizeof(list->count)) / sizeof(struct qla_image_version) = 6 entries actually fit. A larger count walks the image pointer off the end of the stack buffer, reading adjacent kernel stack memory and sending it to the device via qla2x00_write_sfp(). Reject requests whose declared count does not fit in the buffer.
- 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 af733bbfcf667af1871a2735fba2835b0da71efbaffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before a9706d5e754e77515a92bb532bd0d73644979a1faffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 7e3154c97ec15460f715dbbe4097c255cce110b1affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 047f1f7ee6f85bde28abfdda9fa550191ddc0532affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before f93e8039e6fd54a3c027c6184daf00b745b576a0affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 7b22b4cb8822805cef7ba618da6f76e1474d68bdaffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before f2d4f025b67fcbfb2bbbadd3b5a6a43c4b436514affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before de62cf265dbe309f34f144a6cdbca9240317727eaffected · 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-89856Sep 16, 2026 · scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation33Monitor
- ← EarlierCVE-2026-89857Sep 16, 2026 · scsi: qla2xxx: Hold qpair lock when sending NVMe LS reject39Monitor
- Later →CVE-2026-89859Sep 16, 2026 · scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak0Monitor
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 | 047f1f7ee6f85bde28abfdda9fa550191ddc0532 | Vendor (CNA) |
| Linux Linux | 7b22b4cb8822805cef7ba618da6f76e1474d68bd | Vendor (CNA) |
| Linux Linux | 7e3154c97ec15460f715dbbe4097c255cce110b1 | Vendor (CNA) |
| Linux Linux | a9706d5e754e77515a92bb532bd0d73644979a1f | Vendor (CNA) |
| Linux Linux | af733bbfcf667af1871a2735fba2835b0da71efb | Vendor (CNA) |
| Linux Linux | de62cf265dbe309f34f144a6cdbca9240317727e | Vendor (CNA) |
| Linux Linux | f2d4f025b67fcbfb2bbbadd3b5a6a43c4b436514 | Vendor (CNA) |
| Linux Linux | f93e8039e6fd54a3c027c6184daf00b745b576a0 | 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/7b22b4cb8822805cef7ba618da6f76e1474d68bd
- git.kernel.org/stable/c/7e3154c97ec15460f715dbbe4097c255cce110b1
- git.kernel.org/stable/c/a9706d5e754e77515a92bb532bd0d73644979a1f
- git.kernel.org/stable/c/af733bbfcf667af1871a2735fba2835b0da71efb
- git.kernel.org/stable/c/de62cf265dbe309f34f144a6cdbca9240317727e
- git.kernel.org/stable/c/f2d4f025b67fcbfb2bbbadd3b5a6a43c4b436514
- git.kernel.org/stable/c/f93e8039e6fd54a3c027c6184daf00b745b576a0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.