Kernel memory exhaustion via leaked SDIO references
Published May 21, 2024 · Updated May 11, 2026
Resource leak in the Linux kernel SDIO core from 2.6.33 through 6.2-rc8 allows local users to interrupt service via failed initialization. When sdio_add_func() or sdio_init_func() fails before the function is marked present, sdio_remove_func() skips of_node_put() and put_device(), leaking device references. Repeated SDIO error paths are required; the demonstrated effect is accumulating unreferenced kernel objects and memory exhaustion, not code execution.
Summary
What happened
Resource leak in the Linux kernel SDIO core from 2.6.33 through 6.2-rc8 allows local users to interrupt service via failed initialization. When sdio_add_func() or sdio_init_func() fails before the function is marked present, sdio_remove_func() skips of_node_put() and put_device(), leaking device references. Repeated SDIO error paths are required; the demonstrated effect is accumulating unreferenced kernel objects and memory exhaustion, not code execution.
The record
- CVE
- CVE-2023-52730
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=2.6.33
- Affected versionversion=3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 <1e06cf04239e202248c8fa356bf11449dc73cfbd
- Affected versionversion=3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 <30716d9f0fa1766e522cf24c8a456244e4fc9931
- Affected versionversion=3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 <5c7858adada31dbed042448cff6997dd6efc472a
- Affected versionversion=3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 <605d9fb9556f8f5fb4566f4df1480f280f308ded
- Affected versionversion=3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 <761db46b29b496946046d8cb33c7ea6de6bef36e
- Affected versionversion=3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 <92ff03c2563c9b57a027c744750f3b7d2f261c58
- Affected versionversion=3d10a1ba0d37c8f5fd5afcdda00613fbb8a90bf5 <f855d31bb38d663c3ba672345d7cce9324ba3b72
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