CVE-2026-89860: Linux kernel · scsi: qla2xxx: Initialize NVMe abort_work once at submission
Source GCVE Database
Not known to be exploited · CVSS 8.8 High · fixed in f4aaa4a4e6f1da6f3abfd80e1917bef922287177 : patch Linux kernel soon.
Data as of 30 Oct 2026, 16:33 UTC
Thin evidence
One scorer or none| CNA (Linux) | CVSS 3.1 | 8.8 |
|---|
- Patch
- Available – fixed in f4aaa4a4e6f1da6f3abfd80e1917bef922287177, b403700ac62fbf3c310196386e125879a182efcf, 55259e225412721c3cc09e4d95a489542c0c05b0 +5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Initialize NVMe abort_work once at submission qla_nvme_fcp_abort() and qla_nvme_ls_abort() ran INIT_WORK() on priv->abort_work immediately before schedule_work(). INIT_WORK() reinitializes the work_struct, resetting its list head and clearing the pending bit. If an abort is issued more than once for the same command (for example, concurrent transport teardown and a timeout-driven abort), the second INIT_WORK() reinitializes a work item that is already queued, which can corrupt the workqueue list and lead to crashes or a looping worker. Initialize priv->abort_work once at command submission, next to the existing per-command spin_lock_init(&priv->cmd_lock), and leave only schedule_work() in the abort paths. schedule_work() already does nothing when the work item is still pending, so a repeated abort no longer disturbs an in-flight work item. The command is not returned to the transport until the final kref_put()/release callback runs after abort_work has completed, so the work item is idle before priv is reused and the single submission-time INIT_WORK() is safe.
References
- nvd.nist.gov/vuln/detail/CVE-2026-89860 (opens in a new tab)
- git.kernel.org/stable/c/17d9011c96f819e69074f465c04ee79e693de6a1 (opens in a new tab)
- git.kernel.org/stable/c/55259e225412721c3cc09e4d95a489542c0c05b0 (opens in a new tab)
- git.kernel.org/stable/c/67f0d5187c29360388f7e1e503c627ec45d01089 (opens in a new tab)
- git.kernel.org/stable/c/6a1b50c4879c2e6a034e8e85f9c055f0eea157c7 (opens in a new tab)
- git.kernel.org/stable/c/6ee4e3774349fa04bba13e668f3322db47d89b08 (opens in a new tab)
- git.kernel.org/stable/c/7e85f6dbc85616de2172bce8eaf84b387a723cd1 (opens in a new tab)
- git.kernel.org/stable/c/b403700ac62fbf3c310196386e125879a182efcf (opens in a new tab)
- git.kernel.org/stable/c/f4aaa4a4e6f1da6f3abfd80e1917bef922287177 (opens in a new tab)