Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 36 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected cff80645d6d3134260d2ef007a7decb1edcfd4a6 – < e2540dfa3e63512300ca7575c42e9183a6677f26
    • affected cff80645d6d3134260d2ef007a7decb1edcfd4a6 – < d9fa79ccd09204f626d382bdde1b8f5f4c5d03b3
    • affected cff80645d6d3134260d2ef007a7decb1edcfd4a6 – < 62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee
    • affected cff80645d6d3134260d2ef007a7decb1edcfd4a6 – < bb18a346271f87889bd64a3861c9a656a3509ea6
    • affected cff80645d6d3134260d2ef007a7decb1edcfd4a6 – < d283d5d4d9f6d081ddb65e371be26fffeb611c42
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97512 badge
[![CVE-2026-97512](https://cveledger.app/badge/CVE-2026-97512.svg)](https://cveledger.app/cve/CVE-2026-97512)

Record last updated .