CVE-2026-89843: scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 1c820d0900e4aacd5020b989159f6b4b2f7d0d6a, 26bc6a2c235a70bfc9b6de412600208aca820e20, 4fe5790674097897a1af1367d1e384f7e5a62fb7; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1c820d0900e4aacd5020b989159f6b4b2f7d0d6a, 26bc6a2c235a70bfc9b6de412600208aca820e20, 4fe5790674097897a1af1367d1e384f7e5a62fb7; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak Several bsg handlers stage their request/reply in an uninitialized 256-byte on-stack buffer (uint8_t bsg[DMA_POOL_SIZE]) and fill it via sg_copy_to_buffer(), which only copies as many bytes as the user-supplied request payload. When the request is shorter than the structure, the remainder of the buffer is left holding stale stack data. qla2x00_read_fru_status() and qla2x00_read_i2c() then copy the full structure back to the reply payload with sg_copy_from_buffer(), leaking the uninitialized stack bytes to user space. The write/update paths do not copy the buffer back, but can feed uninitialized fields to the device. Zero the stack buffer at declaration in all five handlers, mirroring the heap kzalloc() approach, so short requests can no longer expose stale memory.
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.2affected
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 1c820d0900e4aacd5020b989159f6b4b2f7d0d6aaffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 26bc6a2c235a70bfc9b6de412600208aca820e20affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 5ab32dff910291b5e6bf6223f8a4003536c1800aaffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 947c6bfcf7f5ec924995bec43e3108b98c75b44eaffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 708c0ec1e09c52fee24b74ce9398bf3f8d1c83fdaffected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 4fe5790674097897a1af1367d1e384f7e5a62fb7affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before 7881faf862ee301ecfe3adc0725bd2fa0021cd95affected · git
- 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and later · before b93d3bb3afe1b44489927de1eb4e66e8536a5935affected · git
- before 3.2not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89841Sep 16, 2026 · f2fs: only redirty pinned folios in redirty_blocks31Monitor
- ← EarlierCVE-2026-89842Sep 16, 2026 · scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started0Monitor
- Later →CVE-2026-89844Sep 16, 2026 · scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c820d0900e4aacd5020b989159f6b4b2f7d0d6a | Vendor (CNA) |
| Linux Linux | 26bc6a2c235a70bfc9b6de412600208aca820e20 | Vendor (CNA) |
| Linux Linux | 4fe5790674097897a1af1367d1e384f7e5a62fb7 | Vendor (CNA) |
| Linux Linux | 5ab32dff910291b5e6bf6223f8a4003536c1800a | Vendor (CNA) |
| Linux Linux | 708c0ec1e09c52fee24b74ce9398bf3f8d1c83fd | Vendor (CNA) |
| Linux Linux | 7881faf862ee301ecfe3adc0725bd2fa0021cd95 | Vendor (CNA) |
| Linux Linux | 947c6bfcf7f5ec924995bec43e3108b98c75b44e | Vendor (CNA) |
| Linux Linux | b93d3bb3afe1b44489927de1eb4e66e8536a5935 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/26bc6a2c235a70bfc9b6de412600208aca820e20
- git.kernel.org/stable/c/4fe5790674097897a1af1367d1e384f7e5a62fb7
- git.kernel.org/stable/c/5ab32dff910291b5e6bf6223f8a4003536c1800a
- git.kernel.org/stable/c/708c0ec1e09c52fee24b74ce9398bf3f8d1c83fd
- git.kernel.org/stable/c/7881faf862ee301ecfe3adc0725bd2fa0021cd95
- git.kernel.org/stable/c/947c6bfcf7f5ec924995bec43e3108b98c75b44e
- git.kernel.org/stable/c/b93d3bb3afe1b44489927de1eb4e66e8536a5935
Vendor advisories and official records. Exploit/PoC links are deliberately left out.