{"id":"CVE-2026-97512","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nspi: spi-qcom-qspi: Fix incomplete error handling in runtime PM\n\nThe runtime PM functions had incomplete error handling that could leave the\nsystem in an inconsistent s…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nspi: spi-qcom-qspi: Fix incomplete error handling in runtime PM\n\nThe runtime PM functions had incomplete error handling that could leave the\nsystem in an inconsistent s…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bb18a346271f87889bd64a3861c9a656a3509ea6","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d283d5d4d9f6d081ddb65e371be26fffeb611c42","Linux < 6.12.111","Linux < 6.18.53","Linux (all versions)"],"published":"2026-09-24","updated":"2026-09-24","sourceUpdated":"2026-09-24T17:17:29.100","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-97512","references":[{"url":"https://git.kernel.org/stable/c/62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/bb18a346271f87889bd64a3861c9a656a3509ea6","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/d283d5d4d9f6d081ddb65e371be26fffeb611c42","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-24T16:47:15.862Z","slug":"CVE-2026-97512","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspi: spi-qcom-qspi: Fix incomplete error handling in runtime PM\n\nThe runtime PM functions had incomplete error handling that could leave the\nsystem in an inconsistent state. If any operation failed midway through\nsuspend or resume, some resources would be left in the wrong state while\nothers were already changed, leading to potential clock/power imbalances.\n\nReorder the suspend/resume sequences to avoid brownout risk by ensuring the\nperformance state is set appropriately before clocks are enabled and clocks\nare disabled before dropping the performance state.\n\nFix by adding proper error checking for all operations and using goto-based\ncleanup to ensure all successfully acquired resources are properly released\non any error.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}