Kernel stack disclosure via uninitialized mailbox state
Published Sep 16, 2026 · Updated Sep 16, 2026
Information disclosure in the Linux qla2xxx SCSI driver allows local users to read kernel stack data through sysfs after mailbox failures. The stack-allocated mbx_cmd_t remains uninitialized when qla2x00_mailbox_command() exits early, yet qla2x00_get_firmware_state() copies its fields to the caller. Exposure requires a QLogic adapter, a mailbox failure path, and access to the fw_state or mpi_fw_state sysfs attribute.
Summary
What happened
Information disclosure in the Linux qla2xxx SCSI driver allows local users to read kernel stack data through sysfs after mailbox failures. The stack-allocated mbx_cmd_t remains uninitialized when qla2x00_mailbox_command() exits early, yet qla2x00_get_firmware_state() copies its fields to the caller. Exposure requires a QLogic adapter, a mailbox failure path, and access to the fw_state or mpi_fw_state sysfs attribute.
The record
- CVE
- CVE-2026-89852
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.26
- Affected versionversion=4d4df1932b6b116aecc81039066fec27f2050762 <13d645a2cdb224d27205368f3e3c68bb160daf97
- Affected versionversion=4d4df1932b6b116aecc81039066fec27f2050762 <1f49e861c18caf8eef7f0ad9a2c5034f88a6ba79
- Affected versionversion=4d4df1932b6b116aecc81039066fec27f2050762 <2f847f06bb223aa895eea91fc9e5e2d6314038eb
- Affected versionversion=4d4df1932b6b116aecc81039066fec27f2050762 <9efaa782845b4d5fb3e01242be0d06ebc7428d8f
- Affected versionversion=4d4df1932b6b116aecc81039066fec27f2050762 <9f31de4d07e4cde91dfc24522993a5fbb4d67083
- Affected versionversion=4d4df1932b6b116aecc81039066fec27f2050762 <e6cfb1ee18336aab41a0941d6d3ea5009aaafc05
- Affected versionversion=4d4df1932b6b116aecc81039066fec27f2050762 <f29695b1138ae2539c5cd6cdaba9b1b072aaa81a
- Affected versionversion=4d4df1932b6b116aecc81039066fec27f2050762 <f8fc5cc6b3284506c6ab83c822c48133377668bb
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo