# spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM CVE record · `CVE-2026-97512` - **Identifiers:** `CVE-2026-97512` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **CNA:** Linux - **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md) - **Published:** 24 Sept 2026 - **Updated:** 30 Oct 2026 - **Reviewed by a person:** No Published by the CVE Program (CNA: Linux) at 24 Sept 2026, 16:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. ## Affected products, as the CNA wrote them - Vendor: Linux. Product: Linux. - affected: `cff80645d6d3134260d2ef007a7decb1edcfd4a6 to before e2540dfa3e63512300ca7575c42e9183a6677f26` (git) - affected: `cff80645d6d3134260d2ef007a7decb1edcfd4a6 to before d9fa79ccd09204f626d382bdde1b8f5f4c5d03b3` (git) - affected: `cff80645d6d3134260d2ef007a7decb1edcfd4a6 to before 62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee` (git) - affected: `cff80645d6d3134260d2ef007a7decb1edcfd4a6 to before bb18a346271f87889bd64a3861c9a656a3509ea6` (git) - affected: `cff80645d6d3134260d2ef007a7decb1edcfd4a6 to before d283d5d4d9f6d081ddb65e371be26fffeb611c42` (git) - Other versions: unaffected - Vendor: Linux. Product: Linux. - affected: `5.9` - unaffected: `before 5.9` (semver) - unaffected: `6.1.191 to 6.1.*, inclusive` (semver) - unaffected: `6.6.158 to 6.6.*, inclusive` (semver) - unaffected: `6.12.111 to 6.12.*, inclusive` (semver) - unaffected: `6.18.53 to 6.18.*, inclusive` (semver) - unaffected: `7.2 to *, inclusive` (original_commit_for_fix) - Other versions: affected ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Linux kernel versions from commit cff80645d6d3 up to the fixes listed for each affected branch are affected by a flaw in the spi-qcom-qspi SPI driver's runtime power management. The description says that failures during suspend or resume could leave clocks and power resources in an inconsistent state, but it gives few details on the exact impact or attacker requirements. Upgrade to a fixed Linux kernel release for your branch, or to 6.1.191, 6.6.158, 6.12.111, 6.18.53 or later in those series. Written 12 Nov 2026. ## Not analysed yet We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter. ## Severity and exploitation No source has published a CVSS score for this record yet. - **CISA KEV:** Not listed. - **EPSS:** 0.0016, the 4th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline This record came from the full history of the CVE Program, published 24 Sept 2026. New records show when each source confirmed them. ## Sources - [CVE List: CVE-2026-97512](https://www.cve.org/CVERecord?id=CVE-2026-97512) - [NVD: CVE-2026-97512](https://nvd.nist.gov/vuln/detail/CVE-2026-97512) ### References from the CNA - - - - - Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description. ## Check whether this affects you This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run. - With the agentprime MCP server (), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: - As JSON: - Everything that needs attention now: --- The web page: . Everything for agents: .