CVE-2025-40005: spi: cadence-quadspi: Implement refcount to handle unbind during busy
In the Linux kernel, the following vulnerability has been resolved:
spi: cadence-quadspi: Implement refcount to handle unbind during busy
driver support indirect read and indirect write operation with
assumption no force device removal(unbind) operation. However
force device removal(removal) is still available to root superuser.
Unbinding driver during operation causes kernel crash. This changes
ensure driver able to handle such operation for indirect read and
indirect write by implementing refcount to track attached devices
to the controller and gracefully wait and until attached devices
remove operation completed before proceed with removal operation.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a system when a root user forcibly unbinds the Cadence QuadSPI driver while it is busy with flash read or write activity. The sources describe availability impact, not data theft or remote compromise.
Executive priority
Treat as a targeted availability risk for affected Linux platforms, especially embedded devices where unexpected kernel crashes disrupt operations. Prioritize normal kernel maintenance unless the driver is present on critical systems.
Technical view
The cadence-quadspi SPI driver did not safely handle device unbind during indirect read or indirect write operations. A forced removal could race active operations and crash the kernel. The resolved change adds reference counting so removal waits for attached device operations to complete.
Likely exposure
Exposure is likely limited to Linux systems using the Cadence QuadSPI controller driver, often embedded or SoC platforms. The source bundle lists Linux as affected but does not provide CPEs or a precise product matrix.
Exploitation context
The CVE text says the trigger requires force device removal by the root superuser during driver activity. CISA KEV status is false, and the provided sources do not claim active exploitation or public weaponization.
Researcher notes
Evidence supports a local privileged denial-of-service condition in the Linux cadence-quadspi driver. Severity, CVSS, CWE, and exact affected-version ranges are incomplete in the bundle, so validation should rely on kernel commit presence and vendor advisories.
Mitigation direction
Apply a kernel or vendor update containing the referenced stable fixes.
Validate distro kernel advisories before assuming upstream version coverage.
Avoid forced cadence-quadspi unbind operations on busy systems until patched.
Limit privileged maintenance access to systems using this driver.
Validation and detection
Inventory systems using the cadence-quadspi driver or Cadence QSPI hardware.
Check running kernel builds for the referenced stable commits or vendor backports.
Review crash logs for cadence-quadspi activity around forced unbind events.
Confirm operational procedures do not unbind this driver during flash I/O.
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-2025-40005 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
7Source 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.
Oct 20, 2025, 15:26 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.