CVE-2026-97512 in Linux
Summary
by MITRE • 09/24/2026
In the Linux kernel, the following vulnerability has been resolved:
spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM
The runtime PM functions had incomplete error handling that could leave the system in an inconsistent state. If any operation failed midway through suspend or resume, some resources would be left in the wrong state while others were already changed, leading to potential clock/power imbalances.
Reorder the suspend/resume sequences to avoid brownout risk by ensuring the performance state is set appropriately before clocks are enabled and clocks are disabled before dropping the performance state.
Fix by adding proper error checking for all operations and using goto-based cleanup to ensure all successfully acquired resources are properly released on any error.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 09/24/2026
The Linux kernel driver spi-qcom-qspi manages serial peripheral interface communication for Qualcomm hardware, relying heavily on runtime power management mechanisms to balance performance with energy efficiency. A critical flaw was identified in the implementation of these runtime PM functions, specifically within the suspend and resume sequences. The core issue stems from incomplete error handling that fails to maintain consistency across dependent resources such as clocks and performance states. When an operation encounters a failure midway through either suspending or resuming the device, the system can be left in an inconsistent state where some components have already transitioned while others remain unchanged. This asymmetry creates potential clock and power imbalances that compromise the stability of the hardware interface and the broader system environment.
The technical flaw involves a lack of atomicity in resource management during power transitions. Specifically, the driver did not ensure that performance states were adjusted before enabling clocks or vice versa when errors occurred. In complex embedded systems like those using Qualcomm SoCs, improper sequencing can lead to brownout risks where voltage drops below operational thresholds due to sudden changes in current draw without corresponding adjustments in clock gating or frequency scaling. The original implementation allowed partial execution paths to proceed even after a failure was detected, leaving acquired resources such as enabled clocks active while other dependent states were not updated correctly. This inconsistency violates the principle of clean resource acquisition and release, leading to potential hardware instability or undefined behavior during subsequent power state transitions.
From an operational impact perspective, this vulnerability can result in system hangs, data corruption on SPI buses, or unexpected reboots if the brownout condition triggers a reset. It also poses a risk of increased power consumption because clocks may remain enabled longer than necessary due to failed cleanup routines that do not revert changes made prior to the error point. For systems relying on precise timing and low-power states, such as IoT devices or automotive infotainment systems, these inconsistencies can degrade performance reliability and battery life. The lack of robust error handling means that transient failures during initialization or runtime power management could escalate into persistent system faults requiring manual intervention or rebooting to restore normal operation.
To mitigate this vulnerability, the fix reorders the suspend and resume sequences to enforce a strict dependency chain where performance states are set before clocks are enabled, and clocks are disabled before dropping performance states. This ensures that all resource changes occur in a predictable order that prevents race conditions and brownout scenarios. Additionally, proper error checking was added for every operation within these sequences. The implementation now utilizes goto-based cleanup patterns to guarantee that any resources successfully acquired during the process are properly released if an error occurs later in the sequence. This approach ensures atomicity of the power management operations, maintaining system consistency even when failures happen mid-execution.
This vulnerability aligns with CWE-252, which describes unchecked return values leading to improper resource handling, and CWE-830 regarding inclusion of functionality from potentially compromised sources if error states are not validated correctly in security-critical paths. In the context of MITRE ATT&CK, this relates to T1496 Resource Hijacking where an attacker might exploit timing windows or state inconsistencies to cause denial of service through resource exhaustion or system instability. By enforcing strict ordering and comprehensive cleanup routines, the patch eliminates these attack surfaces related to power management logic flaws. The resolution ensures that the spi-qcom-qspi driver adheres to best practices for kernel-level device drivers, prioritizing robustness and predictability in power state transitions to maintain overall system integrity.