Linux kernel flaw in widely deployed qla2xxx (QLogic HBA) driver with CVSS 9.8; kernel-level compromise or outage could impact many enterprise servers.
CVE-2026-89847
Use-after-free in Linux qla2xxx SCSI driver enabling kernel crash or privilege escalation.
do firstUpgrade to a fixed release: < 4.19, >= 5.10.270 and <= 5.10.*, >= 5.15.221 and <= 5.15.*, >= 6.1.188 and <= 6.1.* (+5 more below).
Is CVE-2026-89847 being exploited?
Not confirmed. CVE-2026-89847 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.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-89847?
CVE-2026-89847 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-89847?
Yes. A fix has been recorded for CVE-2026-89847. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-89847 affect?
CVE-2026-89847 affects Linux kernel (qla2xxx driver), Servers with QLogic Fibre Channel HBAs, Distributions shipping affected kernel builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-89847?
Install vendor/ upstream kernel update for qla2xxx and reboot affected hosts immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free in qla2xxx can cause kernel memory corruption leading to local privilege escalation or kernel panic via crafted IOCB/timeouts.
Patch when possible
- affected>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a and < 71a7b6e3c7f121439f51a058e53d4a8e05b63dec
- affected>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a and < 7257b5e1fb6c9387714f66e01b79ec82b717eede
- affected>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a and < f5b660e0b0d9190d8853c795c2522cc5f8c93003
- affected>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a and < 6e217a9482eabbd8b29847be334c74cf468d3544
- affected>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a and < d6d856c722f40f0694ff755208552e658db6dd42
- affected>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a and < 9fa1d71233a82416492d9c9de9756ebe140fe714
- affected>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a and < 845d4abd92cd2f97551356c8b281ad6e197acb07
- affected>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a and < bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8
- affected4.19
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
- 19 Sept 2026Analysed by vulneraibility.com · 3 days later
- 19 Oct 2026CVE record last updated · 30 days later
- Linkgit.kernel.org /stable/c/71a7b6e3c7f121439f51a058e53d4a8e05b63dec
- Linkgit.kernel.org /stable/c/7257b5e1fb6c9387714f66e01b79ec82b717eede
- Linkgit.kernel.org /stable/c/f5b660e0b0d9190d8853c795c2522cc5f8c93003
- Linkgit.kernel.org /stable/c/6e217a9482eabbd8b29847be334c74cf468d3544
- Linkgit.kernel.org /stable/c/d6d856c722f40f0694ff755208552e658db6dd42
- Linkgit.kernel.org /stable/c/9fa1d71233a82416492d9c9de9756ebe140fe714
- Linkgit.kernel.org /stable/c/845d4abd92cd2f97551356c8b281ad6e197acb07
- Linkgit.kernel.org /stable/c/bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8
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.