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-89852scsi: qla2xxx: Zero mailbox struct in qla2x00_get_firmware_state()

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Zero mailbox struct in qla2x00_get_firmware_state() The mbx_cmd_t is allocated on the stack but left uninitialized. qla2x00_mailbox_command() has several early-return paths (PCI permanent failure, device failed, EEH busy, ISP abort pending, mailbox access timeout, purge mbox) that return without writing the input mailbox registers back into mcp->mb[]. qla2x00_get_firmware_state() then unconditionally copies mcp->mb[1..6] (and mb[12]) into the caller's states[] array regardless of the return value. On such a failure the copied values are uninitialized kernel stack memory, which is then exposed to userspace via the fw_state and mpi_fw_state sysfs handlers. Zero the mailbox struct so a failed query yields deterministic zeroed state instead of leaking stack contents.

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 (16 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 4d4df1932b6b116aecc81039066fec27f2050762 – < f8fc5cc6b3284506c6ab83c822c48133377668bb
    • affected 4d4df1932b6b116aecc81039066fec27f2050762 – < f29695b1138ae2539c5cd6cdaba9b1b072aaa81a
    • affected 4d4df1932b6b116aecc81039066fec27f2050762 – < 13d645a2cdb224d27205368f3e3c68bb160daf97
    • affected 4d4df1932b6b116aecc81039066fec27f2050762 – < 2f847f06bb223aa895eea91fc9e5e2d6314038eb
    • affected 4d4df1932b6b116aecc81039066fec27f2050762 – < 1f49e861c18caf8eef7f0ad9a2c5034f88a6ba79
    • affected 4d4df1932b6b116aecc81039066fec27f2050762 – < e6cfb1ee18336aab41a0941d6d3ea5009aaafc05
    • affected 4d4df1932b6b116aecc81039066fec27f2050762 – < 9f31de4d07e4cde91dfc24522993a5fbb4d67083
    • affected 4d4df1932b6b116aecc81039066fec27f2050762 – < 9efaa782845b4d5fb3e01242be0d06ebc7428d8f
  • Linux · Linux

    • affected 2.6.26
    • unaffected < 2.6.26
    • 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-89852 badge
[![CVE-2026-89852](https://cveledger.app/badge/CVE-2026-89852.svg)](https://cveledger.app/cve/CVE-2026-89852)

Record last updated .