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

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

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

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.

The Linux kernel CVE team has assigned CVE-2026-97512 to this issue.


Affected and fixed versions
===========================

	Fixed in 6.12.111 with commit 62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee
	Fixed in 6.18.53 with commit bb18a346271f87889bd64a3861c9a656a3509ea6
	Fixed in 7.2 with commit d283d5d4d9f6d081ddb65e371be26fffeb611c42

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-97512
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/spi/spi-qcom-qspi.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee
	https://git.kernel.org/stable/c/bb18a346271f87889bd64a3861c9a656a3509ea6
	https://git.kernel.org/stable/c/d283d5d4d9f6d081ddb65e371be26fffeb611c42