Service interruption via permanent DMA resource leak
Published Oct 4, 2025 · Updated Oct 4, 2025
Resource leak in the QUP SPI driver in affected Linux kernels allows local users to interrupt service through device removal. The spi_qup_remove callback returns when runtime power management cannot wake the device, bypassing DMA cleanup and permanently leaking those resources. Reaching the flaw requires local low-privileged access and a QUP SPI device-removal path; accumulated leaks exhaust resources and interrupt service.
Summary
What happened
Resource leak in the QUP SPI driver in affected Linux kernels allows local users to interrupt service through device removal. The spi_qup_remove callback returns when runtime power management cannot wake the device, bypassing DMA cleanup and permanently leaking those resources. Reaching the flaw requires local low-privileged access and a QUP SPI device-removal path; accumulated leaks exhaust resources and interrupt service.
The record
- CVE
- CVE-2023-53567
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.15
- Affected versionversion=64ff247a978facc437d40f0c9b754675846a98f0 <2d0f63077f481f11a07f20eab1c1f4367dfaef32
- Affected versionversion=64ff247a978facc437d40f0c9b754675846a98f0 <49c17fccae36505550c9121891722fff337f148a
- Affected versionversion=64ff247a978facc437d40f0c9b754675846a98f0 <55ecdcd12bc176b86fecbcb125ac814ac8fe857a
- Affected versionversion=64ff247a978facc437d40f0c9b754675846a98f0 <61f49171a43ab1f80c73c5c88c508770c461e0f2
- Affected versionversion=64ff247a978facc437d40f0c9b754675846a98f0 <8632384337038b97910c2f7bb5a3f377aa68d001
- Affected versionversion=64ff247a978facc437d40f0c9b754675846a98f0 <bc88243bbe6140d289bb32b4ee4607ba5ce1124a
- Affected versionversion=64ff247a978facc437d40f0c9b754675846a98f0 <f345d4d71e87d878437417ffbb9a7d4e16d235eb
- Affected versionversion=64ff247a978facc437d40f0c9b754675846a98f0 <fd53f41bd86daa39b454fd4637a908ff2123547f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo