In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Unlink NVMe…

Why it is Amber

• CVSS 8.8 high
• On your watchlist: linux kernel

References

• https://git.kernel.org/stable/c/925a9129a514b7c3bc0a8af01e51868adbb9a83e
• https://git.kernel.org/stable/c/a95fc5f1c12bba1dbff72bd2611e7fad0758831b
• https://git.kernel.org/stable/c/c55d649a6cc246c3ccd5d118faea230c46b60f35
• https://git.kernel.org/stable/c/cbbf1484496aac86038e67ac984949af58009d4b
• https://git.kernel.org/stable/c/e46160a5d4fa59bf4d5f3412b6b5cb79edb967dd

Original description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Unlink NVMe unsol ctx before freeing on LS reject error qla_nvme_xmt_ls_rsp() obtains uctx, which was linked into fcport->unsol_ctx_head by qla2xxx_process_purls_iocb() and is still linked when the NVMe transport calls back to transmit the LS response. On the error (out:) path the function frees uctx with kfree() but never removes it from the list. This leaves a freed node in fcport->unsol_ctx_head: the next list_add_tail() for that fcport writes through the freed node, and a subsequent list_del() can corrupt the list or panic. Unlink uctx with list_del() before kfree() on the error path, matching the other free sites in qla_nvme_release_lsrsp_cmd_kref() and qla2xxx_process_purls_pkt(). qla2x00_rel_sp() in the failure path only returns the SRB to its pool and does not invoke sp->put_fn, so the out: path is the sole free and uctx is always still linked there.