CVE-2026-89860

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.

CVSS v3 8.8 HIGH

8.8^/10

CVSS v3 : HIGH

Vector :

Exploitability : 2.8 / Impact : 5.9

Attack Vector ADJACENT_NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://git.kernel.org/stable/c/67f0d5187c29360388f7e1e503c627ec45d01089
https://git.kernel.org/stable/c/6a1b50c4879c2e6a034e8e85f9c055f0eea157c7
https://git.kernel.org/stable/c/7e85f6dbc85616de2172bce8eaf84b387a723cd1
https://git.kernel.org/stable/c/b403700ac62fbf3c310196386e125879a182efcf
https://git.kernel.org/stable/c/f4aaa4a4e6f1da6f3abfd80e1917bef922287177

Configurations

No configuration.

History

16 Sep 2026, 15:18

Type	Values Removed	Values Added
CVSS	v2 : ~~unknown~~ v3 : ~~unknown~~	v2 : unknown v3 : 8.8

Information

Published : 2026-09-16 11:16

Updated : 2026-09-16 15:18

NVD link : CVE-2026-89860

Mitre link : CVE-2026-89860

CVE.ORG link : CVE-2026-89860

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2026-89860", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.8, "attackVector": "ADJACENT_NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.8}]}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "e473b3074104ee09227cfbba5f872e3ea15dd280", "lessThan": "b403700ac62fbf3c310196386e125879a182efcf", "versionType": "git"}, {"status": "affected", "version": "e473b3074104ee09227cfbba5f872e3ea15dd280", "lessThan": "6a1b50c4879c2e6a034e8e85f9c055f0eea157c7", "versionType": "git"}, {"status": "affected", "version": "e473b3074104ee09227cfbba5f872e3ea15dd280", "lessThan": "67f0d5187c29360388f7e1e503c627ec45d01089", "versionType": "git"}, {"status": "affected", "version": "e473b3074104ee09227cfbba5f872e3ea15dd280", "lessThan": "f4aaa4a4e6f1da6f3abfd80e1917bef922287177", "versionType": "git"}, {"status": "affected", "version": "e473b3074104ee09227cfbba5f872e3ea15dd280", "lessThan": "7e85f6dbc85616de2172bce8eaf84b387a723cd1", "versionType": "git"}], "programFiles": ["drivers/scsi/qla2xxx/qla_nvme.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "4.17"}, {"status": "unaffected", "version": "0", "lessThan": "4.17", "versionType": "semver"}, {"status": "unaffected", "version": "6.6.157", "versionType": "semver", "lessThanOrEqual": "6.6.*"}, {"status": "unaffected", "version": "6.12.110", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.51", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.2.5", "versionType": "semver", "lessThanOrEqual": "7.2.*"}, {"status": "unaffected", "version": "7.3-rc1", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/scsi/qla2xxx/qla_nvme.c"], "defaultStatus": "affected"}]}], "published": "2026-09-16T11:16:53.957", "references": [{"url": "https://git.kernel.org/stable/c/67f0d5187c29360388f7e1e503c627ec45d01089", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/6a1b50c4879c2e6a034e8e85f9c055f0eea157c7", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/7e85f6dbc85616de2172bce8eaf84b387a723cd1", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/b403700ac62fbf3c310196386e125879a182efcf", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/f4aaa4a4e6f1da6f3abfd80e1917bef922287177", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Received", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Initialize NVMe abort_work once at submission\n\nqla_nvme_fcp_abort() and qla_nvme_ls_abort() ran INIT_WORK() on\npriv->abort_work immediately before schedule_work(). INIT_WORK()\nreinitializes the work_struct, resetting its list head and clearing the\npending bit. If an abort is issued more than once for the same command\n(for example, concurrent transport teardown and a timeout-driven abort),\nthe second INIT_WORK() reinitializes a work item that is already queued,\nwhich can corrupt the workqueue list and lead to crashes or a looping\nworker.\n\nInitialize priv->abort_work once at command submission, next to the\nexisting per-command spin_lock_init(&priv->cmd_lock), and leave only\nschedule_work() in the abort paths. schedule_work() already does nothing\nwhen the work item is still pending, so a repeated abort no longer\ndisturbs an in-flight work item. The command is not returned to the\ntransport until the final kref_put()/release callback runs after\nabort_work has completed, so the work item is idle before priv is reused\nand the single submission-time INIT_WORK() is safe."}], "lastModified": "2026-09-16T15:18:13.790", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}