CVE-2026-89850: scsi: qla2xxx: Don't query firmware state while chip is down
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 178d984e8875292582e4295cf559b2b11d3c9325, 22f44f77da496bc355479c08a0a9dbc9ad42ba42, 7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749; 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 178d984e8875292582e4295cf559b2b11d3c9325, 22f44f77da496bc355479c08a0a9dbc9ad42ba42, 7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749; 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: Don't query firmware state while chip is down qla2x00_fw_state_show() initializes rval to QLA_FUNCTION_FAILED and jumps to the out: label when the chip is down or EEH is busy. The out: block then re-issued qla2x00_get_firmware_state() because rval != QLA_SUCCESS, defeating the chip-down/EEH-busy guards and issuing a mailbox command (outside optrom_mutex) during ISP reset or PCI error recovery, which can hang the adapter. It also turned a normal in-lock mailbox failure into a second unsynchronized mailbox attempt. Make the out: fallback only mark the firmware state as unknown. The mailbox is now issued at most once, inside optrom_mutex, and only when the chip is up and not EEH-busy.
- 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
- 4.20affected
- b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and later · before 178d984e8875292582e4295cf559b2b11d3c9325affected · git
- b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and later · before cba780c01f72f8585ca81ad7304097f8b12ef339affected · git
- b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and later · before 22f44f77da496bc355479c08a0a9dbc9ad42ba42affected · git
- b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and later · before b6a30baa29695fa0eaba4a3a04435a3c1a5cb63daffected · git
- b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and later · before 7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749affected · git
- b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and later · before a194684853dceaa1d6b7a9a02bc12f479232ad9baffected · git
- b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and later · before a6374b508893de15fee78583a95f5099d7812e85affected · git
- b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and later · before e0cebe20dcffbed9c078fe30e2d18cd5046d9effaffected · git
- before 4.20not 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-89848Sep 16, 2026 · scsi: qla2xxx: Quiesce response IRQ before freeing request queue32Monitor
- ← EarlierCVE-2026-89849Sep 16, 2026 · scsi: qla2xxx: Reject non-SCSI SRB on status IOCB fast path35Monitor
- Later →CVE-2026-89851Sep 16, 2026 · scsi: qla2xxx: Fix FCE trace enable parsing in debugfs0Monitor
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 | 178d984e8875292582e4295cf559b2b11d3c9325 | Vendor (CNA) |
| Linux Linux | 22f44f77da496bc355479c08a0a9dbc9ad42ba42 | Vendor (CNA) |
| Linux Linux | 7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749 | Vendor (CNA) |
| Linux Linux | a194684853dceaa1d6b7a9a02bc12f479232ad9b | Vendor (CNA) |
| Linux Linux | a6374b508893de15fee78583a95f5099d7812e85 | Vendor (CNA) |
| Linux Linux | b6a30baa29695fa0eaba4a3a04435a3c1a5cb63d | Vendor (CNA) |
| Linux Linux | cba780c01f72f8585ca81ad7304097f8b12ef339 | Vendor (CNA) |
| Linux Linux | e0cebe20dcffbed9c078fe30e2d18cd5046d9eff | 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/22f44f77da496bc355479c08a0a9dbc9ad42ba42
- git.kernel.org/stable/c/7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749
- git.kernel.org/stable/c/a194684853dceaa1d6b7a9a02bc12f479232ad9b
- git.kernel.org/stable/c/a6374b508893de15fee78583a95f5099d7812e85
- git.kernel.org/stable/c/b6a30baa29695fa0eaba4a3a04435a3c1a5cb63d
- git.kernel.org/stable/c/cba780c01f72f8585ca81ad7304097f8b12ef339
- git.kernel.org/stable/c/e0cebe20dcffbed9c078fe30e2d18cd5046d9eff
Vendor advisories and official records. Exploit/PoC links are deliberately left out.