CVE-2026-97528

8.8

Linux · Kernel

A use-after-free vulnerability in the Linux kernel SCSI qla2xxx driver allows for potential memory corruption or system panics due to improper list management during error handling.

Executive summary

A memory corruption vulnerability in the Linux kernel SCSI qla2xxx driver poses a significant risk of system instability and potential denial of service.

Vulnerability

The vulnerability exists in the qla_nvme_xmt_ls_rsp function, where an unlinked memory context is freed without being removed from a linked list. This results in a use-after-free condition that can be triggered by an unauthenticated attacker on the adjacent network, leading to list corruption or kernel panic.

Business impact

The flaw carries a CVSS score of 8.8, reflecting its potential to cause severe system disruptions. Successful exploitation results in a denial of service, which can cause significant downtime for critical infrastructure relying on these SCSI drivers. The ability for an attacker on an adjacent network to trigger a kernel panic poses a direct threat to system availability and reliability.

Remediation

Immediate Action: Update the Linux kernel to version 6.18.53, 7.2.7, or later, as provided by your distribution vendor.

Proactive Monitoring: Monitor system logs for kernel oops, panic events, or SCSI driver errors that may indicate exploitation attempts or memory corruption.

Compensating Controls: Ensure that network segmentation is strictly enforced to limit access to the adjacent network, thereby reducing the attack surface for this vulnerability.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

Given the severity of potential kernel-level impacts, administrators should prioritize applying the provided kernel patches across all affected environments. While there is currently no evidence of active exploitation, the risk of system instability necessitates prompt remediation to maintain operational continuity.

More Linux CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources