CVE-2026-97527
Last modified
CVE-2026-97527 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock The fcport->unsol_ctx_head list is modified from several contexts without a common lock. Entries are added in qla2xxx_process_purls_iocb() from the response queue ISR (under the qpair qp_lock), while they are removed from qla2xxx_process_purls_pkt() (DPC/purex worker), qla_nvme_xmt_ls_rsp() (NVMe-FC transport callback) and qla_nvme_release_lsrsp_cmd_kref() (SRB completion).
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock The fcport->unsol_ctx_head list is modified from several contexts without a common lock. Entries are added in qla2xxx_process_purls_iocb() from the response queue ISR (under the qpair qp_lock), while they are removed from qla2xxx_process_purls_pkt() (DPC/purex worker), qla_nvme_xmt_ls_rsp() (NVMe-FC transport callback) and qla_nvme_release_lsrsp_cmd_kref() (SRB completion). The qpair qp_lock cannot serialize this per-fcport list since multiqueue adapters add entries through different qpairs, so a concurrent add and delete (or two concurrent deletes) can corrupt the list pointers. Introduce a dedicated per-fcport spinlock, unsol_ctx_lock, initialized in qla2x00_alloc_fcport(), and take it around every list_add_tail()/list_del() on unsol_ctx_head. The add nests under the existing qp_lock; no delete path takes qp_lock, so the lock order is consistent and deadlock free.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 875386b98857822b77ac7f95bdf367b70af5b78c, < b211d138cad86f749826d6132db6388eded992d8; >= 875386b98857822b77ac7f95bdf367b70af5b78c, < 4d8ad6bc8cc5eff1870cef00a0d611f38f8b6bd0; >= 875386b98857822b77ac7f95bdf367b70af5b78c, < 76da0c43c63eb0496649e372ac64466364d0fe7d |
| Linux | Linux | 6.6 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-97527?
How severe is CVE-2026-97527?
How do I fix CVE-2026-97527?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97521In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97522In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97523In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-97524In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-97525In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-97526In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97528In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-97529In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9753The $_internalApplyOplogUpdate aggregation pipeline stage ca…8.1
- CVE-2026-97530In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97531In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-97532In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-97527?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
