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

> Incomplete error handling in the Qualcomm QSPI driver can cause system instability or crashes during power management transitions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103796, BELL-CVE-2026-97512, DEBIAN-CVE-2026-97512, GHSA-m235-m239-qwv2, UBUNTU-CVE-2026-97512

## What is CVE-2026-97512?

CVE-2026-97512 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-97512?


## How do I fix CVE-2026-97512?

Apply the vendor's patch.

## Is CVE-2026-97512 being exploited?

There is no known exploitation of CVE-2026-97512 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97512 and fix it if it is affected.

What it is: CVE-2026-97512 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97512 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97512/ (Markdown: https://insights.sbomify.com/CVE-2026-97512/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97512
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97512
- OSV: https://osv.dev/vulnerability/CVE-2026-97512

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97512/
Summaries are generated and may contain mistakes; the official description above is the record.