CVE-2026-97535 Linux CVE debrief

Who should care

Linux kernel developers, administrators responsible for maintaining and securing Linux-based systems, and security teams should assess exposure and verify patch deployment to prevent exploitation. This includes reviewing system configurations, monitoring system logs for potential exploitation attempts, and ensuring that the Linux kernel version is up-to-date and patched. Additionally, operators and platform administrators should be aware of the potential

Why it matters

The CVE-2026-97535 vulnerability in the Linux kernel allows for an out-of-bounds write in the qla2xxx SCSI driver, which can lead to memory corruption and potential system instability. Linux kernel developers and administrators should assess exposure and verify patch deployment to prevent exploitation.

• Memory corruption can lead to system crashes or instability.
• Potential for denial-of-service (DoS) attacks.
• Possible data corruption or loss.
• Verification of patch deployment is necessary to prevent exploitation.

Technical summary

The vulnerability arises from the qla24xx_control_vp() function not properly checking the vp_index against the VP_CTRL IOCB bitmap size, which can lead to memory corruption. The fix involves rejecting a vp_index that cannot be represented in the IOCB bitmap in qla24xx_control_vp(), and adding a defensive ARRAY_SIZE() guard in qla25xx_ctrlvp_iocb() before the write. This ensures that the vp_index is within the bounds of the vp_idx_map array, preventing out-of-bounds writes and potential memory corruption. Affected product deployments should be reviewed, and patch deployment verified to prevent exploitation.

Defensive priority

High

Recommended defensive actions

• Review and apply the Linux kernel patch to ensure the vp_index is within the bounds of the vp_idx_map array.
• Monitor system logs for potential exploitation attempts.
• Verify that the Linux kernel version is up-to-date and patched.
• Perform a thorough review of system configurations and assess exposure to this vulnerability.
• Implement compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The vulnerability was resolved in the Linux kernel by adding a check to ensure the vp_index is within the bounds of the vp_idx_map array. The fix involves rejecting a vp_index that cannot be represented in the IOCB bitmap in qla24xx_control_vp(), and adding a defensive ARRAY_SIZE() guard in qla25xx_ctrlvp_iocb() before the write.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.