Linux
scsi: qla2xxx: Avoid double completion in async IOCB timeout
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().
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 71a7b6e3c7f121439f51a058e53d4a8e05b63dec
- >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 7257b5e1fb6c9387714f66e01b79ec82b717eede
- >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < f5b660e0b0d9190d8853c795c2522cc5f8c93003
- >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 6e217a9482eabbd8b29847be334c74cf468d3544
- >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < d6d856c722f40f0694ff755208552e658db6dd42
- >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 9fa1d71233a82416492d9c9de9756ebe140fe714
- >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < 845d4abd92cd2f97551356c8b281ad6e197acb07
- >= f6145e86d21fccd59bbb87bc1e1eb076658fd79a, < bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8
Fixed in 71a7b6e3c7f121439f51a058e53d4a8e05b63dec, 7257b5e1fb6c9387714f66e01b79ec82b717eede, f5b660e0b0d9190d8853c795c2522cc5f8c93003, 6e217a9482eabbd8b29847be334c74cf468d3544, d6d856c722f40f0694ff755208552e658db6dd42, 9fa1d71233a82416492d9c9de9756ebe140fe714, 845d4abd92cd2f97551356c8b281ad6e197acb07, bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8
- 4.19
Fixed in 0, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5, 7.3
Mitigation
Upgrade Linux to 71a7b6e3c7f121439f51a058e53d4a8e05b63dec or 7257b5e1fb6c9387714f66e01b79ec82b717eede or f5b660e0b0d9190d8853c795c2522cc5f8c93003 or 6e217a9482eabbd8b29847be334c74cf468d3544 or d6d856c722f40f0694ff755208552e658db6dd42 or 9fa1d71233a82416492d9c9de9756ebe140fe714 or 845d4abd92cd2f97551356c8b281ad6e197acb07 or bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8 or later.
Upgrade Linux to 0 or 5.10.270 or 5.15.221 or 6.1.188 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.