CVE-2026-89847: scsi: qla2xxx: Avoid double completion in async IOCB timeout
Noroxi assessment
Priority: Monitor (action score 39/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.69% (FIRST EPSS); higher than 53.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 6e217a9482eabbd8b29847be334c74cf468d3544, 71a7b6e3c7f121439f51a058e53d4a8e05b63dec, 7257b5e1fb6c9387714f66e01b79ec82b717eede; 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 6e217a9482eabbd8b29847be334c74cf468d3544, 71a7b6e3c7f121439f51a058e53d4a8e05b63dec, 7257b5e1fb6c9387714f66e01b79ec82b717eede; 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: Avoid double completion in async IOCB timeout qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then call sp->done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking whether the SRB was actually found and removed. If the response ISR completes the same handle first, it removes the SRB under qp_lock_ptr and runs sp->done() -> complete(sp->comp). The submitter qla24xx_control_vp() wakes from wait_for_completion(), clears sp->comp, drops its reference and returns, reclaiming the on-stack completion. The timer reference keeps the SRB alive across the timeout handler, but not the submitter's stack. The timeout then issues a second sp->done() -> qla_ctrlvp_sp_done(), which evaluates "if (sp->comp) complete(sp->comp)"; with the pointer loaded before the submitter's NULL store, complete() writes into the freed stack frame, a use-after-free. Track whether this path removed the SRB from outstanding_cmds and only call sp->done() when it did, so the command is completed exactly once by whichever path owns it. This mirrors the sp_found guard already used in qla24xx_abort_iocb_timeout().
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.6% · 53th percentile
- CWE
- —
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 4.19affected
- f6145e86d21fccd59bbb87bc1e1eb076658fd79a and later · before 71a7b6e3c7f121439f51a058e53d4a8e05b63decaffected · git
- f6145e86d21fccd59bbb87bc1e1eb076658fd79a and later · before 7257b5e1fb6c9387714f66e01b79ec82b717eedeaffected · git
- f6145e86d21fccd59bbb87bc1e1eb076658fd79a and later · before f5b660e0b0d9190d8853c795c2522cc5f8c93003affected · git
- f6145e86d21fccd59bbb87bc1e1eb076658fd79a and later · before 6e217a9482eabbd8b29847be334c74cf468d3544affected · git
- f6145e86d21fccd59bbb87bc1e1eb076658fd79a and later · before d6d856c722f40f0694ff755208552e658db6dd42affected · git
- f6145e86d21fccd59bbb87bc1e1eb076658fd79a and later · before 9fa1d71233a82416492d9c9de9756ebe140fe714affected · git
- f6145e86d21fccd59bbb87bc1e1eb076658fd79a and later · before 845d4abd92cd2f97551356c8b281ad6e197acb07affected · git
- f6145e86d21fccd59bbb87bc1e1eb076658fd79a and later · before bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8affected · git
- before 4.19not 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-89845Sep 16, 2026 · scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry()0Monitor
- ← EarlierCVE-2026-89846Sep 16, 2026 · scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read36Monitor
- Later →CVE-2026-89848Sep 16, 2026 · scsi: qla2xxx: Quiesce response IRQ before freeing request queue32Monitor
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 | 6e217a9482eabbd8b29847be334c74cf468d3544 | Vendor (CNA) |
| Linux Linux | 71a7b6e3c7f121439f51a058e53d4a8e05b63dec | Vendor (CNA) |
| Linux Linux | 7257b5e1fb6c9387714f66e01b79ec82b717eede | Vendor (CNA) |
| Linux Linux | 845d4abd92cd2f97551356c8b281ad6e197acb07 | Vendor (CNA) |
| Linux Linux | 9fa1d71233a82416492d9c9de9756ebe140fe714 | Vendor (CNA) |
| Linux Linux | bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8 | Vendor (CNA) |
| Linux Linux | d6d856c722f40f0694ff755208552e658db6dd42 | Vendor (CNA) |
| Linux Linux | f5b660e0b0d9190d8853c795c2522cc5f8c93003 | 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
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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/71a7b6e3c7f121439f51a058e53d4a8e05b63dec
- git.kernel.org/stable/c/7257b5e1fb6c9387714f66e01b79ec82b717eede
- git.kernel.org/stable/c/845d4abd92cd2f97551356c8b281ad6e197acb07
- git.kernel.org/stable/c/9fa1d71233a82416492d9c9de9756ebe140fe714
- git.kernel.org/stable/c/bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8
- git.kernel.org/stable/c/d6d856c722f40f0694ff755208552e658db6dd42
- git.kernel.org/stable/c/f5b660e0b0d9190d8853c795c2522cc5f8c93003
Vendor advisories and official records. Exploit/PoC links are deliberately left out.