CVE-2026-89847: Linux Vulnerability (CVSS 9.8)

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid double completion in async IOCB timeout qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then call sp->done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking whether the SRB was actually found and removed. If the response ISR completes the same handle first, it removes the SRB under qp_lock_ptr and runs sp->done() -> complete(sp->comp). The submitter qla24xx_control_vp() wakes from wait_for_completion(), clears sp->comp, drops its reference and returns, reclaiming the on-stack completion. The timer reference keeps the SRB alive across the timeout handler, but not the submitter's stack. The timeout then issues a second sp->done() -> qla_ctrlvp_sp_done(), which evaluates "if (sp->comp) complete(sp->comp)"; with the pointer loaded before the submitter's NULL store, complete() writes into the freed stack frame, a use-after-free. Track whether this path removed the SRB from outstanding_cmds and only call sp->done() when it did, so the command is completed exactly once by whichever path owns it. This mirrors the sp_found guard already used in qla24xx_abort_iocb_timeout().

Metrics

CVSS 3.1

9.8/10

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

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 71a7b6e3c7f121439f51a058e53d4a8e05b63dec; >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 7257b5e1fb6c9387714f66e01b79ec82b717eede; >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < f5b660e0b0d9190d8853c795c2522cc5f8c93003; >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 6e217a9482eabbd8b29847be334c74cf468d3544; >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < d6d856c722f40f0694ff755208552e658db6dd42; >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 9fa1d71233a82416492d9c9de9756ebe140fe714; >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 845d4abd92cd2f97551356c8b281ad6e197acb07; >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8
Linux	Linux	4.19

References

Timeline

Published: Sep 16, 2026
Last Modified: Sep 16, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-89847?

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid double completion in async IOCB timeout qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then call sp->done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking whether the SRB was actually found and removed. If the response ISR completes the same handle first, it removes the SRB under qp_lock_ptr and runs sp->done() -> complete(sp->comp). The submitter qla24xx_control_vp() wakes from wait_for_completion(), clears sp->comp, drops its reference and returns, reclaiming the on-stack completion. The timer reference keeps the SRB alive across the timeout handler, but not the submitter's stack. The timeout then issues a second sp->done() -> qla_ctrlvp_sp_done(), which evaluates "if (sp->comp) complete(sp->comp)"; with the pointer loaded before the submitter's NULL store, complete() writes into the freed stack frame, a use-after-free. Track whether this path removed the SRB from outstanding_cmds and only call sp->done() when it did, so the command is completed exactly once by whichever path owns it. This mirrors the sp_found guard already used in qla24xx_abort_iocb_timeout().

How severe is CVE-2026-89847?

CVE-2026-89847 has a CVSS score of 9.8/10 (CRITICAL severity).

How do I fix CVE-2026-89847?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →