Skip to main content
VulnerabilityPublished Updated

CVE-2026-89860: Linux kernel · scsi: qla2xxx: Initialize NVMe abort_work once at submission

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-89860· High 8.8

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

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.18.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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e473b3074104ee09227cfbba5f872e3ea15dd280, < f4aaa4a4e6f1da6f3abfd80e1917bef922287177
Fixed in
  • f4aaa4a4e6f1da6f3abfd80e1917bef922287177
LinuxLinuxAffected
  • ≥ e473b3074104ee09227cfbba5f872e3ea15dd280, < b403700ac62fbf3c310196386e125879a182efcf
Fixed in
  • b403700ac62fbf3c310196386e125879a182efcf
LinuxLinuxAffected
  • ≥ e473b3074104ee09227cfbba5f872e3ea15dd280, < 55259e225412721c3cc09e4d95a489542c0c05b0
Fixed in
  • 55259e225412721c3cc09e4d95a489542c0c05b0
LinuxLinuxAffected
  • ≥ e473b3074104ee09227cfbba5f872e3ea15dd280, < 67f0d5187c29360388f7e1e503c627ec45d01089
Fixed in
  • 67f0d5187c29360388f7e1e503c627ec45d01089
LinuxLinuxAffected
  • ≥ e473b3074104ee09227cfbba5f872e3ea15dd280, < 17d9011c96f819e69074f465c04ee79e693de6a1
Fixed in
  • 17d9011c96f819e69074f465c04ee79e693de6a1
LinuxLinuxAffected
  • ≥ e473b3074104ee09227cfbba5f872e3ea15dd280, < 7e85f6dbc85616de2172bce8eaf84b387a723cd1
Fixed in
  • 7e85f6dbc85616de2172bce8eaf84b387a723cd1

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

Community reviews

Loading reviews…