CVE-2026-97512 Linux CVE debrief

Who should care

Linux kernel maintainers, users, and administrators should assess exposure and prioritize verification of affected systems, especially those using the spi-qcom-qspi component. They should review Linux kernel updates, monitor for potential clock/power imbalances, and plan vendor-supported updates or mitigations. Affected operator, platform, vulnerability-management, and security-team impact should be considered when prioritizing verification and remediation

Why it matters

A vulnerability in the Linux kernel's spi: spi-qcom-qspi component could lead to system inconsistencies if runtime PM operations fail midway. Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.

• Verification of affected systems and potential clock/power imbalances
• Assessment of exposure for Linux kernel users and administrators
• Prioritization of Linux kernel updates for spi-qcom-qspi component

Technical summary

The Linux kernel's spi: spi-qcom-qspi component had incomplete error handling in runtime PM functions, potentially leaving the system in an inconsistent state. The issue was resolved by reordering suspend/resume sequences and adding proper error checking. This change ensures that performance states are set appropriately before clocks are enabled and clocks are disabled before dropping the performance state, mitigating the risk of brownout. The vulnerability could lead to system inconsistencies and potential clock/power imbalances if runtime PM operations fail midway.

Defensive priority

Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems, especially those using the spi-qcom-qspi component.

Recommended defensive actions

• Review Linux kernel updates for spi-qcom-qspi component
• Assess system exposure and prioritize verification
• Monitor for potential clock/power imbalances
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but specific affected versions and exploitation details are not provided. The vulnerability was resolved by reordering suspend/resume sequences and adding proper error checking in the Linux kernel's spi: spi-qcom-qspi component. Defenders should verify affected system deployments, review official advisories, and plan vendor-supported updates or mitigations. The vulnerability could lead to system inconsistencies and potential clock/power imbalances if runtime PM The N1

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.