LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53567: spi: qup: Don't skip cleanup in remove's error path

In the Linux kernel, the following vulnerability has been resolved: spi: qup: Don't skip cleanup in remove's error path Returning early in a platform driver's remove callback is wrong. In this case the dma resources are not released in the error path. this is never retried later and so this is a permanent leak. To fix this, only skip hardware disabling if waking the device fails.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel resource-leak issue in the Qualcomm QUP SPI driver. During driver removal, an error path could skip cleanup and permanently leave DMA resources allocated. The public data does not show remote exploitation, privilege escalation, or active exploitation.

Executive priority

Treat as routine kernel maintenance unless the organization operates Qualcomm-based Linux platforms at scale. No public source in the bundle supports emergency action, but affected device fleets should receive normal kernel update priority.

Technical view

The issue is in the spi-qup platform driver remove callback. Returning early after a device wake failure skipped DMA cleanup. Kernel stable commits change the logic so cleanup is still performed, only skipping hardware disable when waking fails.

Likely exposure

Exposure appears limited to Linux systems using affected kernels with the spi-qup driver and relevant Qualcomm QUP SPI hardware or platform configuration. General Linux servers without this driver or hardware are unlikely to be exposed.

Exploitation context

The source bundle marks KEV as false and provides no evidence of exploitation in the wild. The described impact is a persistent DMA resource leak on a driver removal error path, not a directly documented attacker workflow.

Researcher notes

The public record lacks CVSS, CWE, and detailed affected CPEs. Version data in the bundle is hard to interpret, so confirm exposure through vendor advisories and commit presence rather than name-only kernel matching.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable fixes.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Prioritize affected embedded, mobile, or Qualcomm-platform Linux deployments.
  • If patching is delayed, verify whether spi-qup is present and actually used.

Validation and detection

  • Inventory running kernel versions and vendor patch levels.
  • Check whether the spi-qup driver is built, loaded, or required.
  • Compare kernel source or changelog against the referenced stable commits.
  • Review device lifecycle logs for driver removal or DMA cleanup errors.
Prepared
Confidence
medium
Sources
10

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-2023-53567 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
0ADP providers
9Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux64ff247a978facc437d40f0c9b754675846a98f0, 64ff247a978facc437d40f0c9b754675846a98f0, 64ff247a978facc437d40f0c9b754675846a98f0, 64ff247a978facc437d40f0c9b754675846a98f0, 64ff247a978facc437d40f0c9b754675846a98f0, 64ff247a978facc437d40f0c9b754675846a98f0, 64ff247a978facc437d40f0c9b754675846a98f0, 64ff247a978facc437d40f0c9b754675846a98f0unaffected
LinuxLinux3.15, 0, 4.19.283, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

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