Strix
74.8K

CVE-2026-97512

UnknownEPSS 0.16%

Last modified

CVE-2026-97512 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.16%

4.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= cff80645d6d3134260d2ef007a7decb1edcfd4a6, < e2540dfa3e63512300ca7575c42e9183a6677f26; >= cff80645d6d3134260d2ef007a7decb1edcfd4a6, < d9fa79ccd09204f626d382bdde1b8f5f4c5d03b3; >= cff80645d6d3134260d2ef007a7decb1edcfd4a6, < 62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee; >= cff80645d6d3134260d2ef007a7decb1edcfd4a6, < bb18a346271f87889bd64a3861c9a656a3509ea6; >= cff80645d6d3134260d2ef007a7decb1edcfd4a6, < d283d5d4d9f6d081ddb65e371be26fffeb611c42
LinuxLinux5.9

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97512?
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.
How severe is CVE-2026-97512?
Severity scoring for CVE-2026-97512 is pending analysis. The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.
How do I fix CVE-2026-97512?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-97512?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST