Linux
scsi: qla2xxx: Initialize NVMe abort_work once at submission
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= e473b3074104ee09227cfbba5f872e3ea15dd280, < 6ee4e3774349fa04bba13e668f3322db47d89b08
- >= e473b3074104ee09227cfbba5f872e3ea15dd280, < 55259e225412721c3cc09e4d95a489542c0c05b0
- >= e473b3074104ee09227cfbba5f872e3ea15dd280, < 17d9011c96f819e69074f465c04ee79e693de6a1
- >= e473b3074104ee09227cfbba5f872e3ea15dd280, < b403700ac62fbf3c310196386e125879a182efcf
- >= e473b3074104ee09227cfbba5f872e3ea15dd280, < 6a1b50c4879c2e6a034e8e85f9c055f0eea157c7
- >= e473b3074104ee09227cfbba5f872e3ea15dd280, < 67f0d5187c29360388f7e1e503c627ec45d01089
- >= e473b3074104ee09227cfbba5f872e3ea15dd280, < f4aaa4a4e6f1da6f3abfd80e1917bef922287177
- >= e473b3074104ee09227cfbba5f872e3ea15dd280, < 7e85f6dbc85616de2172bce8eaf84b387a723cd1
Fixed in 6ee4e3774349fa04bba13e668f3322db47d89b08, 55259e225412721c3cc09e4d95a489542c0c05b0, 17d9011c96f819e69074f465c04ee79e693de6a1, b403700ac62fbf3c310196386e125879a182efcf, 6a1b50c4879c2e6a034e8e85f9c055f0eea157c7, 67f0d5187c29360388f7e1e503c627ec45d01089, f4aaa4a4e6f1da6f3abfd80e1917bef922287177, 7e85f6dbc85616de2172bce8eaf84b387a723cd1
- 4.17
Fixed in 0, 5.10.273, 5.15.224, 6.1.191, 6.6.157, 6.12.110, 6.18.51, 7.2.5, 7.3
Mitigation
Upgrade Linux to 6ee4e3774349fa04bba13e668f3322db47d89b08 or 55259e225412721c3cc09e4d95a489542c0c05b0 or 17d9011c96f819e69074f465c04ee79e693de6a1 or b403700ac62fbf3c310196386e125879a182efcf or 6a1b50c4879c2e6a034e8e85f9c055f0eea157c7 or 67f0d5187c29360388f7e1e503c627ec45d01089 or f4aaa4a4e6f1da6f3abfd80e1917bef922287177 or 7e85f6dbc85616de2172bce8eaf84b387a723cd1 or later.
Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.157 or 6.12.110 or 6.18.51 or 7.2.5 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.