The cadence-QuadSPI driver can access hardware registers while the controller clock is disabled during the unbind process. This unclocked register access can trigger a fault within the kernel and lead to a crash. The flaw does not allow arbitrary code execution or remote exploitation, but it can cause a denial of service for users who have local privileged access. The weakness arises from a missing pre‑condition check before disabling the controller.

All Linux kernel builds that contain the cadence-quadspi driver are affected. Platforms that use Cadence QuadSPI controllers may also be impacted; the specific SoC families are inferred from typical deployments and not explicitly stated in the CVE data. Kernels that lack the recent commit that guarantees the controller is runtime resumed before it is powered down during unbind are vulnerable.

A CVSS score of 7.1 is available, EPSS <1%, and the vulnerability is not listed in CISA KEV. The vulnerability requires an attacker to have the capability to unbind the driver, normally limited to root or kernel module execution, making it mainly local and confined to availability rather than confidentiality or integrity. No widespread exploitation has been reported.