CVE-2026-89842: scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 2935b730211c5c1433aa6101fa3b55df2b63869a, 7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120, ac4b019ac07844d3f67ea5e48b1d982b2170d1a7; 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 2935b730211c5c1433aa6101fa3b55df2b63869a, 7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120, ac4b019ac07844d3f67ea5e48b1d982b2170d1a7; 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: Skip NVMe LS reject IOCB when FW not started qla_nvme_xmt_ls_rsp() bails out to the out: label when firmware is not started (!ha->flags.fw_started), but the out: path unconditionally calls qla_nvme_ls_reject_iocb(), which ends in qla2x00_start_iocbs() and an unconditional doorbell write to the request queue in-pointer register. This rings the firmware doorbell and queues an IOCB that stopped or resetting firmware cannot consume, and touches MMIO during the reset/EEH window where fw_started is also clear. Only emit the LS reject IOCB (and ring the doorbell) when fw_started is set; otherwise just clean up and return. The post-allocation failure cases (SRB alloc / qla2x00_start_sp() failure) run with firmware started and still send the reject. Apply the same guard to the reject emission in qla2xxx_process_purls_pkt().
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
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.
Is your version affected? Check itNoroxi 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
- 6.6affected
- 875386b98857822b77ac7f95bdf367b70af5b78c and later · before 2935b730211c5c1433aa6101fa3b55df2b63869aaffected · git
- 875386b98857822b77ac7f95bdf367b70af5b78c and later · before 7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120affected · git
- 875386b98857822b77ac7f95bdf367b70af5b78c and later · before ac4b019ac07844d3f67ea5e48b1d982b2170d1a7affected · git
- 875386b98857822b77ac7f95bdf367b70af5b78c and later · before e9bfb56e2c1bda49d3c5442d824569d71eec07e2affected · git
- 875386b98857822b77ac7f95bdf367b70af5b78c and later · before f7e46ebffc5781aab3f1f5a5d4350addbb5833f4affected · git
- before 6.6not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
- 6.12.110 and later · up to and including 6.12.*not affected · semver
- 6.18.51 and later · up to and including 6.18.*not 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-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-89840Sep 16, 2026 · f2fs: validate MOVE_RANGE destination size28Monitor
- ← EarlierCVE-2026-89841Sep 16, 2026 · f2fs: only redirty pinned folios in redirty_blocks31Monitor
- Later →CVE-2026-89843Sep 16, 2026 · scsi: qla2xxx: Zero-init bsg stack buffers 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 | 2935b730211c5c1433aa6101fa3b55df2b63869a | Vendor (CNA) |
| Linux Linux | 7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120 | Vendor (CNA) |
| Linux Linux | ac4b019ac07844d3f67ea5e48b1d982b2170d1a7 | Vendor (CNA) |
| Linux Linux | e9bfb56e2c1bda49d3c5442d824569d71eec07e2 | Vendor (CNA) |
| Linux Linux | f7e46ebffc5781aab3f1f5a5d4350addbb5833f4 | 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.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).
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)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.