CVE-2026-97512: spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Fixed version: Linux Linux 62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee, bb18a346271f87889bd64a3861c9a656a3509ea6, d283d5d4d9f6d081ddb65e371be26fffeb611c42; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee, bb18a346271f87889bd64a3861c9a656a3509ea6, d283d5d4d9f6d081ddb65e371be26fffeb611c42; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 24, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.9affected
- cff80645d6d3134260d2ef007a7decb1edcfd4a6 and later · before e2540dfa3e63512300ca7575c42e9183a6677f26affected · git
- cff80645d6d3134260d2ef007a7decb1edcfd4a6 and later · before d9fa79ccd09204f626d382bdde1b8f5f4c5d03b3affected · git
- cff80645d6d3134260d2ef007a7decb1edcfd4a6 and later · before 62dd3b8d3a92eb4e080b2ae491c2a5341654c1eeaffected · git
- cff80645d6d3134260d2ef007a7decb1edcfd4a6 and later · before bb18a346271f87889bd64a3861c9a656a3509ea6affected · git
- cff80645d6d3134260d2ef007a7decb1edcfd4a6 and later · before d283d5d4d9f6d081ddb65e371be26fffeb611c42affected · git
- before 5.9not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
- 6.12.111 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97509Sep 24, 2026 · thunderbolt: Keep XDomain reference during the lifetime of a service35Monitor
- ← EarlierCVE-2026-97510Sep 24, 2026 · thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response()0Monitor
- Later →CVE-2026-97513Sep 24, 2026 · media: chips-media: wave5: Release m2m_ctx after Instance Removed from List31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 62dd3b8d3a92eb4e080b2ae491c2a5341654c1ee | Vendor (CNA) |
| Linux Linux | bb18a346271f87889bd64a3861c9a656a3509ea6 | Vendor (CNA) |
| Linux Linux | d283d5d4d9f6d081ddb65e371be26fffeb611c42 | Vendor (CNA) |
| Linux Linux | d9fa79ccd09204f626d382bdde1b8f5f4c5d03b3 | Vendor (CNA) |
| Linux Linux | e2540dfa3e63512300ca7575c42e9183a6677f26 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.