CVE-2026-46203: spi: cadence-quadspi: fix unclocked access on unbind
In the Linux kernel, the following vulnerability has been resolved:
spi: cadence-quadspi: fix unclocked access on unbind
Make sure that the controller is runtime resumed before disabling it
during driver unbind to avoid an unclocked register access.
This issue was flagged by Sashiko when reviewing a controller
deregistration fix.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects the Cadence QuadSPI driver during driver unbind. The bug can cause register access while the controller is not clocked. The source bundle does not provide CVSS, business impact, or active exploitation evidence, so urgency should be based on whether affected kernels run on systems using this controller.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency, unless critical embedded or appliance platforms use this driver. The missing severity and exploit data limit urgency confidence.
Technical view
The fix ensures the cadence-quadspi controller is runtime resumed before being disabled during driver unbind, preventing unclocked register access. The CVE lists Linux as affected and references two stable kernel commits. No CWE, CVSS vector, crash impact, privilege boundary, or exploitability details are provided.
Likely exposure
Exposure is most likely on Linux systems using the cadence-quadspi SPI controller driver in affected kernel versions or downstream kernels carrying the vulnerable code. The bundle does not identify specific distributions, devices, or cloud images.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not claim active exploitation. The described trigger is a driver unbind or deregistration path, not a remote network-facing attack surface.
Researcher notes
Key unknowns are practical impact, whether unclocked access causes denial of service or hardware faults, and downstream backport status. Focus validation on affected driver presence and whether the stable commits are included.
Mitigation direction
Check kernel or distribution advisories for CVE-2026-46203 coverage.
Apply vendor kernel updates containing the referenced stable fixes.
Prioritize systems that use the Cadence QuadSPI controller driver.
Avoid ad hoc workarounds unless vendor guidance recommends them.
Validation and detection
Inventory kernels and devices using the cadence-quadspi driver.
Confirm the deployed kernel includes one of the referenced fixes.
Review distro changelogs for CVE-2026-46203 backports.
Regression-test driver lifecycle behavior in staging after patching.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-46203 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 28, 2026, 09:40 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.