{"id":"CVE-2026-89857","published":"2026-09-16T11:16:53.573","lastModified":"2026-09-16T15:18:13.657","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Hold qpair lock when sending NVMe LS reject\n\nqla_nvme_ls_reject_iocb() allocates from and advances the request ring\nthrough __qla2x00_alloc_iocbs() (which assumes the hardware_lock is\nheld) and qla2x00_start_iocbs() (which advances the ring and rings the\nrequest-in doorbell), but takes no lock itself. Two of its callers\ninvoke it without the producer lock held:\n\n - qla_nvme_xmt_ls_rsp(), the NVMe-FC .xmt_ls_rsp transport callback, on\n   its error path, and\n\n - qla2xxx_process_purls_pkt(), run from the purex work/DPC context.\n\nBoth use ha->base_qpair, whose qp_lock_ptr is hardware_lock, so they can\nrun concurrently with normal I/O submission on the base ring and corrupt\nthe ring producer state, leading to duplicated or dropped commands. The\nthird caller, qla2xxx_process_purls_iocb(), runs inside\nqla24xx_process_response_queue() with the qpair lock already held and is\nsafe; that is also why the lock cannot be taken inside the helper itself\n(it would recursively re-acquire hardware_lock on the response path).\n\nTake qp_lock_ptr around the two unlocked callers and document the helper\nas caller-locked. Both run in process context, so spin_lock_irqsave() is\nused and nothing in the locked region sleeps.","cvssScore":9.8,"cvssSeverity":"CRITICAL","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/11834e5773e20fd3742d7eb900876e66b9e7d029","tags":[]},{"url":"https://git.kernel.org/stable/c/7eb618877503edbf17aa65e357a81bda1fc8f163","tags":[]},{"url":"https://git.kernel.org/stable/c/b02ff132017b28222187ebcf95ce7f4cb576cd36","tags":[]},{"url":"https://git.kernel.org/stable/c/b3a362466db6b8ec47cc537ac641ac197fa69b5d","tags":[]},{"url":"https://git.kernel.org/stable/c/f743488e4a203049f27ec5d8cd0caccc483af01e","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":{"summary":"This vulnerability in the Linux kernel's qla2xxx driver allows for race conditions when handling NVMe LS reject messages, potentially leading to command duplication or loss.","exploitability":"Exploitation requires concurrent execution of specific driver functions without proper locking, making it moderately difficult but feasible under certain conditions.","blast_radius":"If exploited, this could lead to system instability and data corruption in environments using affected storage controllers.","remediation":"Apply the latest kernel updates that address this vulnerability to ensure proper locking mechanisms are enforced.","tags":["kernel","storage","race-condition","lock"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-09-23T08:44:09.633Z"}}