{"id":"CVE-2026-89857","title":"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() (whic…","summary":"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() (whic…","severity":"critical","cvss":9.8,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","vendor":"Linux","product":"Linux","affected":["Linux >= 875386b98857822b77ac7f95bdf367b70af5b78c < 7eb618877503edbf17aa65e357a81bda1fc8f163","Linux >= 875386b98857822b77ac7f95bdf367b70af5b78c < b3a362466db6b8ec47cc537ac641ac197fa69b5d","Linux >= 875386b98857822b77ac7f95bdf367b70af5b78c < 11834e5773e20fd3742d7eb900876e66b9e7d029","Linux >= 875386b98857822b77ac7f95bdf367b70af5b78c < b02ff132017b28222187ebcf95ce7f4cb576cd36","Linux >= 875386b98857822b77ac7f95bdf367b70af5b78c < f743488e4a203049f27ec5d8cd0caccc483af01e","Linux 6.6"],"published":"2026-09-16","updated":"2026-09-16","sourceUpdated":"2026-09-16T15:18:13.657","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-89857","references":[{"url":"https://git.kernel.org/stable/c/11834e5773e20fd3742d7eb900876e66b9e7d029","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/7eb618877503edbf17aa65e357a81bda1fc8f163","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/b02ff132017b28222187ebcf95ce7f4cb576cd36","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/b3a362466db6b8ec47cc537ac641ac197fa69b5d","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/f743488e4a203049f27ec5d8cd0caccc483af01e","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-16T10:53:53.992Z","epss":0.00671,"epssPercentile":0.49867,"slug":"CVE-2026-89857","body":"## Overview\n\nIn 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"midnight","depthScore":54,"depthScoreParts":{"impact":53.9,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[{"seq":205194,"id":"CVE-2026-89857","ts":1789570705672,"field":"cvss","old":null,"new":"9.8"},{"seq":205193,"id":"CVE-2026-89857","ts":1789570705672,"field":"severity","old":"none","new":"critical"}]}