CVE-2026-89850 — scsi: qla2xxx: Don't query firmware state while chip is down
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.
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 |
≥ b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and < 178d984e8875292582e4295cf559b2b11d3c9325≥ b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and < cba780c01f72f8585ca81ad7304097f8b12ef339≥ b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and < 22f44f77da496bc355479c08a0a9dbc9ad42ba42≥ b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and < b6a30baa29695fa0eaba4a3a04435a3c1a5cb63d≥ b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and < 7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749≥ b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and < a194684853dceaa1d6b7a9a02bc12f479232ad9b≥ b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and < a6374b508893de15fee78583a95f5099d7812e85≥ b6faaaf796d7bfb00e32ca5c905d55cc43e89448 and < e0cebe20dcffbed9c078fe30e2d18cd5046d9eff and 1 moreversion 4.20 |
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/cba780c01f72f8585ca81ad7304097f8b12ef339
- nvd.nist.gov/vuln/detail/CVE-2026-89850
- github.com/advisories/GHSA-52m9-92gj-jg2v
- git.kernel.org/stable/c/22f44f77da496bc355479c08a0a9dbc9ad42ba42
- git.kernel.org/stable/c/7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749
- git.kernel.org/stable/c/178d984e8875292582e4295cf559b2b11d3c9325
- git.kernel.org/stable/c/e0cebe20dcffbed9c078fe30e2d18cd5046d9eff
- git.kernel.org/stable/c/a6374b508893de15fee78583a95f5099d7812e85
- git.kernel.org/stable/c/b6a30baa29695fa0eaba4a3a04435a3c1a5cb63d
- git.kernel.org/stable/c/a194684853dceaa1d6b7a9a02bc12f479232ad9b
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 2d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 2d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 2d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 2d
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 2d
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 2d
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-89850 is "scsi: qla2xxx: Don't query firmware state while chip is down", 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.