Linux kernel qla2xxx driver bug affects many servers using QLogic NVMe‑FC HBAs; can corrupt storage I/O and disrupt operations across environments.
CVE-2026-89857
qla2xxx kernel bug can corrupt NVMe‑FC request ring causing data loss/DoS
do firstUpgrade to a fixed release: < 6.6, >= 6.6.157 and <= 6.6.*, >= 6.12.110 and <= 6.12.*, >= 6.18.51 and <= 6.18.* (+2 more below).
Is CVE-2026-89857 being exploited?
Not confirmed. CVE-2026-89857 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.
How severe is CVE-2026-89857?
CVE-2026-89857 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-89857?
Yes. A fix has been recorded for CVE-2026-89857. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-89857 affect?
CVE-2026-89857 affects Linux kernel (qla2xxx driver), QLogic/Marvell Fibre Channel HBAs, Servers using NVMe-over-FC SANs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-89857?
Apply kernel updates containing the qla2xxx fix and reboot affected hosts; quiesce SAN I/O before update.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Corrupts qla2xxx request ring leading to duplicated/dropped NVMe‑FC commands → storage data corruption, I/O loss, or host DoS.
Immediate action required
- affected>= 875386b98857822b77ac7f95bdf367b70af5b78c and < 7eb618877503edbf17aa65e357a81bda1fc8f163
- affected>= 875386b98857822b77ac7f95bdf367b70af5b78c and < b3a362466db6b8ec47cc537ac641ac197fa69b5d
- affected>= 875386b98857822b77ac7f95bdf367b70af5b78c and < 11834e5773e20fd3742d7eb900876e66b9e7d029
- affected>= 875386b98857822b77ac7f95bdf367b70af5b78c and < b02ff132017b28222187ebcf95ce7f4cb576cd36
- affected>= 875386b98857822b77ac7f95bdf367b70af5b78c and < f743488e4a203049f27ec5d8cd0caccc483af01e
- affected6.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
timeline
- 16 Sept 2026Published
- 18 Sept 2026Analysed by vulneraibility.com · 2 days later
- 19 Oct 2026CVE record last updated · 31 days later
- Linkgit.kernel.org /stable/c/7eb618877503edbf17aa65e357a81bda1fc8f163
- Linkgit.kernel.org /stable/c/b3a362466db6b8ec47cc537ac641ac197fa69b5d
- Linkgit.kernel.org /stable/c/11834e5773e20fd3742d7eb900876e66b9e7d029
- Linkgit.kernel.org /stable/c/b02ff132017b28222187ebcf95ce7f4cb576cd36
- Linkgit.kernel.org /stable/c/f743488e4a203049f27ec5d8cd0caccc483af01e
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.