What is CVE-2026-97527?

CVE-2026-97527 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10, affecting Linux kernel versions from 6.6 onward and patched in 6.12.112, 6.18.53, 7.2.7 and others. CVE-2026-97527 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-97527?

CVE-2026-97527 has a CVSS score of 8.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-97527?

Yes, CVE-2026-97527 has been patched. Fixed versions include 6.12.112, 6.18.53, 7.2.7 and others. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-97527 actively exploited?

CVE-2026-97527 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-97527

High

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.

Package Linux Kernel

Published 2026-09-25

Last modified 2026-10-03

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

8.8

out of 10

High

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.6 and later are affected. Fixed in 6.12.112, 6.18.53, 7.2.7, 7.3-rc1 and their respective stable series.

Affected from

≥ 6.6

Fixed in

✓ 6.12.112 6.12.x ✓ 6.18.53 6.18.x ✓ 7.2.7 7.2.x ✓ 7.3-rc1

References

4 total

Details

CVE ID CVE-2026-97527

Severity High

CVSS score 8.8 / 10

CVSS version 3.1

Published 2026-09-25

Modified 2026-10-03

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-97527?

CVE-2026-97527 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10 . It affects Linux kernel versions from 6.6 onward and has been patched in 6.12.112, 6.18.53, 7.2.7 and others. CVE-2026-97527 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-97527?

CVE-2026-97527 has a CVSS score of 8.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-97527?

Yes. CVE-2026-97527 has been patched. Fixed versions include 6.12.112, 6.18.53, 7.2.7 and others. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-97527 actively exploited?

No. CVE-2026-97527 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.