CVE-2026-89847

scsi: qla2xxx: Avoid double completion in async IOCB timeout

State
Published
Severity
9.8 Critical
Published
Sep 16, 2026
Updated
Oct 19, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

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().

Scores

CVSSScoreVectorSource
3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • f6145e86d21fccd59bbb87bc1e1eb076658fd79a to before 71a7b6e3c7f121439f51a058e53d4a8e05b63decAffected
  • f6145e86d21fccd59bbb87bc1e1eb076658fd79a to before 7257b5e1fb6c9387714f66e01b79ec82b717eedeAffected
  • f6145e86d21fccd59bbb87bc1e1eb076658fd79a to before f5b660e0b0d9190d8853c795c2522cc5f8c93003Affected
  • f6145e86d21fccd59bbb87bc1e1eb076658fd79a to before 6e217a9482eabbd8b29847be334c74cf468d3544Affected
  • f6145e86d21fccd59bbb87bc1e1eb076658fd79a to before d6d856c722f40f0694ff755208552e658db6dd42Affected
  • f6145e86d21fccd59bbb87bc1e1eb076658fd79a to before 9fa1d71233a82416492d9c9de9756ebe140fe714Affected
  • f6145e86d21fccd59bbb87bc1e1eb076658fd79a to before 845d4abd92cd2f97551356c8b281ad6e197acb07Affected
  • f6145e86d21fccd59bbb87bc1e1eb076658fd79a to before bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8Affected
LinuxLinux
  • 4.19Affected
  • before 4.19Not affected
  • 5.10.270 through 5.10.*Not affected
  • 5.15.221 through 5.15.*Not affected
  • 6.1.188 through 6.1.*Not affected
  • 6.6.157 through 6.6.*Not affected
  • 6.12.110 through 6.12.*Not affected
  • 6.18.51 through 6.18.*Not affected
  • 7.2.5 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.