CVE-2026-97512: spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM

Published Sep 24, 2026
·
Updated

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.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    In the Linux kernel spi-qcom-qspi runtime PM implementation, add error checking for all operations and use goto-based cleanup so that all successfully acquired resources are released on any suspend or resume error; set the performance state before enabling clocks and disable clocks before dropping the performance state.

Event History

Sep 24, 2026
CVE Published
via MITRE·04:05 PM
Data Sourced
via MITRE·04:05 PM
Description
Data Sourced
via NVD·05:17 PM
Description

Frequently Asked Questions

1

What systems are most likely to be exposed to this issue?

Systems running the Linux kernel with the Qualcomm QSPI SPI driver and using runtime power management are the relevant population. The issue is triggered when suspend or resume operations encounter an error partway through their sequence.

2

What is the practical impact of a failed runtime PM transition?

A partial suspend or resume can leave clocks, power-related resources, and the performance state out of sync. This can create clock or power imbalances and carries a brownout risk.

3

What should be done if a runtime PM operation fails?

Use a kernel version containing the fix, which adds error checks and cleanup for resources acquired before a failure. The corrected ordering sets the performance state before enabling clocks and disables clocks before dropping the performance state.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203