What is CVE-2026-89860?

CVE-2026-89860 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10, affecting Linux kernel versions from 4.17 onward and patched in 6.6.157, 6.12.110, 6.18.51 and others. CVE-2026-89860 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-89860?

CVE-2026-89860 has a CVSS score of 8.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-89860?

Yes, CVE-2026-89860 has been patched. Fixed versions include 6.6.157, 6.12.110, 6.18.51 and others. If you are running Linux kernel 4.17 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-89860 actively exploited?

CVE-2026-89860 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-89860

High

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.

Package Linux Kernel

Published 2026-09-16

Last modified 2026-09-16

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

8.8

out of 10

High

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 4.17 and later are affected. Fixed in 6.6.157, 6.12.110, 6.18.51, 7.2.5, 7.3-rc1 and their respective stable series.

Affected from

≥ 4.17

Fixed in

✓ 6.6.157 6.6.x ✓ 6.12.110 6.12.x ✓ 6.18.51 6.18.x ✓ 7.2.5 7.2.x ✓ 7.3-rc1

References

5 total

Details

CVE ID CVE-2026-89860

Severity High

CVSS score 8.8 / 10

CVSS version 3.1

Published 2026-09-16

Modified 2026-09-16

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-89860?

CVE-2026-89860 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10 . It affects Linux kernel versions from 4.17 onward and has been patched in 6.6.157, 6.12.110, 6.18.51 and others. CVE-2026-89860 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-89860?

CVE-2026-89860 has a CVSS score of 8.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-89860?

Yes. CVE-2026-89860 has been patched. Fixed versions include 6.6.157, 6.12.110, 6.18.51 and others. If you are running Linux kernel 4.17 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-89860 actively exploited?

No. CVE-2026-89860 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.