{"id":"CVE-2026-97527","published":"2026-09-25T11:17:02.873","lastModified":"2026-09-25T15:17:58.053","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock\n\nThe fcport->unsol_ctx_head list is modified from several contexts without\na common lock. Entries are added in qla2xxx_process_purls_iocb() from the\nresponse queue ISR (under the qpair qp_lock), while they are removed from\nqla2xxx_process_purls_pkt() (DPC/purex worker), qla_nvme_xmt_ls_rsp()\n(NVMe-FC transport callback) and qla_nvme_release_lsrsp_cmd_kref() (SRB\ncompletion). The qpair qp_lock cannot serialize this per-fcport list since\nmultiqueue adapters add entries through different qpairs, so a concurrent\nadd and delete (or two concurrent deletes) can corrupt the list pointers.\n\nIntroduce a dedicated per-fcport spinlock, unsol_ctx_lock, initialized in\nqla2x00_alloc_fcport(), and take it around every list_add_tail()/list_del()\non unsol_ctx_head. The add nests under the existing qp_lock; no delete path\ntakes qp_lock, so the lock order is consistent and deadlock free.","cvssScore":8.8,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:A/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/4d8ad6bc8cc5eff1870cef00a0d611f38f8b6bd0","tags":[]},{"url":"https://git.kernel.org/stable/c/76da0c43c63eb0496649e372ac64466364d0fe7d","tags":[]},{"url":"https://git.kernel.org/stable/c/b211d138cad86f749826d6132db6388eded992d8","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":{"summary":"This vulnerability arises from the lack of proper synchronization in the scsi: qla2xxx driver, leading to potential corruption of the unsol_ctx_head list. It matters because concurrent modifications can cause data races and system instability.","exploitability":"Exploitation requires access to the affected SCSI device and concurrent operations on the unsol_ctx_head list. It is moderately difficult to exploit due to the need for specific timing and access conditions.","blast_radius":"If exploited, the vulnerability could lead to denial of service (DoS) conditions or potential data corruption affecting the storage subsystem.","remediation":"Upgrade to the specific version 5.10.103 or later, as published in the advisory.","detection":"No reliable host or network indicator is derivable from the published description.","tags":["dos","storage","kernel"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-09-29T09:04:43.379Z"}}