GHSA-M235-M239-QWV2
Vulnerability from github – Published: 2026-09-24 18:31 – Updated: 2026-09-24 18:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-97512"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-24T17:17:29Z",
"severity": null
},
"details": "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 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.",
"id": "GHSA-m235-m239-qwv2",
"modified": "2026-09-24T18:31:35Z",
"published": "2026-09-24T18:31:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97512"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bb18a346271f87889bd64a3861c9a656a3509ea6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d283d5d4d9f6d081ddb65e371be26fffeb611c42"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.