Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89850scsi: qla2xxx: Don't query firmware state while chip is down

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b6faaaf796d7bfb00e32ca5c905d55cc43e89448 – < 178d984e8875292582e4295cf559b2b11d3c9325
    • affected b6faaaf796d7bfb00e32ca5c905d55cc43e89448 – < cba780c01f72f8585ca81ad7304097f8b12ef339
    • affected b6faaaf796d7bfb00e32ca5c905d55cc43e89448 – < 22f44f77da496bc355479c08a0a9dbc9ad42ba42
    • affected b6faaaf796d7bfb00e32ca5c905d55cc43e89448 – < b6a30baa29695fa0eaba4a3a04435a3c1a5cb63d
    • affected b6faaaf796d7bfb00e32ca5c905d55cc43e89448 – < 7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749
    • affected b6faaaf796d7bfb00e32ca5c905d55cc43e89448 – < a194684853dceaa1d6b7a9a02bc12f479232ad9b
    • affected b6faaaf796d7bfb00e32ca5c905d55cc43e89448 – < a6374b508893de15fee78583a95f5099d7812e85
    • affected b6faaaf796d7bfb00e32ca5c905d55cc43e89448 – < e0cebe20dcffbed9c078fe30e2d18cd5046d9eff
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89850 badge
[![CVE-2026-89850](https://cveledger.app/badge/CVE-2026-89850.svg)](https://cveledger.app/cve/CVE-2026-89850)

Record last updated .