LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26806: spi: cadence-qspi: remove system-wide suspend helper calls from runtime PM hooks

In the Linux kernel, the following vulnerability has been resolved: spi: cadence-qspi: remove system-wide suspend helper calls from runtime PM hooks The ->runtime_suspend() and ->runtime_resume() callbacks are not expected to call spi_controller_suspend() and spi_controller_resume(). Remove calls to those in the cadence-qspi driver. Those helpers have two roles currently: - They stop/start the queue, including dealing with the kworker. - They toggle the SPI controller SPI_CONTROLLER_SUSPENDED flag. It requires acquiring ctlr->bus_lock_mutex. Step one is irrelevant because cadence-qspi is not queued. Step two however has two implications: - A deadlock occurs, because ->runtime_resume() is called in a context where the lock is already taken (in the ->exec_op() callback, where the usage count is incremented). - It would disallow all operations once the device is auto-suspended. Here is a brief call tree highlighting the mutex deadlock: spi_mem_exec_op() ... spi_mem_access_start() mutex_lock(&ctlr->bus_lock_mutex) cqspi_exec_mem_op() pm_runtime_resume_and_get() cqspi_resume() spi_controller_resume() mutex_lock(&ctlr->bus_lock_mutex) ... spi_mem_access_end() mutex_unlock(&ctlr->bus_lock_mutex) ...

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause systems using the Cadence QSPI driver to hang during flash operations after runtime power management activity. The likely business impact is availability, not confirmed data theft or remote compromise. Exposure appears hardware- and configuration-specific.

Executive priority

Treat this as a targeted availability risk for embedded Linux fleets, appliances, or products using Cadence QSPI. It is not supported as actively exploited by the provided sources, but affected platforms should be patched through normal kernel maintenance.

Technical view

The cadence-qspi driver called system-wide SPI suspend/resume helpers from runtime PM callbacks. During spi_mem_exec_op(), bus_lock_mutex may already be held when runtime resume calls spi_controller_resume(), causing a mutex deadlock. The source also notes operations could be blocked after auto-suspend.

Likely exposure

Organizations are most likely exposed on Linux systems that use the Cadence QSPI SPI controller driver, especially embedded or appliance platforms. The source lists Linux 6.7, 6.7.9, and 6.8-related affected version data; downstream vendor backports must be verified.

Exploitation context

The provided sources do not show active exploitation, public weaponization, or CISA KEV listing. The issue is described as a kernel driver deadlock triggered through runtime power management and SPI memory operations, suggesting local/system-behavior exposure rather than internet-facing exploitability.

Researcher notes

Evidence is limited to the CVE record and kernel stable commits. No CVSS, CWE, exploit status, or vendor-specific downstream package information is provided. Validate exposure by driver use and kernel patch lineage, not by version string alone.

Mitigation direction

  • Review vendor kernel advisories for your distribution or device platform.
  • Update to a kernel build containing the referenced stable fixes.
  • Prioritize systems using Cadence QSPI flash or SPI memory paths.
  • If patching is delayed, monitor vendor guidance for operational workarounds.

Validation and detection

  • Inventory kernels and devices using the cadence-qspi driver.
  • Check whether deployed kernels include the referenced stable commits.
  • Review logs for SPI, QSPI, runtime PM, or suspend/resume failures.
  • Test affected hardware after update for flash access and suspend behavior.
Prepared
Confidence
medium
Sources
4

Public sources used

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-2024-26806 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0578a6dbfe7514db7134501cf93acc21cf13e479, 0578a6dbfe7514db7134501cf93acc21cf13e479unaffected
LinuxLinux6.7, 0, 6.7.9, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.