Local denial of service via initialization memory leak
Published Oct 4, 2025 · Updated Oct 4, 2025
Memory leak in the Linux kernel IPMI system-interface driver allows local users to exhaust kernel memory during module initialization. In try_smi_init(), an error after allocating new_smi->si_sm but before handler registration bypasses shutdown_smi(), leaving the allocation unreleased. The published assessment requires local low-privileged access; the record does not identify the trigger, and repeated failures can interrupt service through kernel-memory exhaustion.
Summary
What happened
Memory leak in the Linux kernel IPMI system-interface driver allows local users to exhaust kernel memory during module initialization. In try_smi_init(), an error after allocating new_smi->si_sm but before handler registration bypasses shutdown_smi(), leaving the allocation unreleased. The published assessment requires local low-privileged access; the record does not identify the trigger, and repeated failures can interrupt service through kernel-memory exhaustion.
The record
- CVE
- CVE-2023-53611
- 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=4.18
- Affected versionversion=7960f18a56475bf2177c5ff56c72eb4c12c56440 <09cb2a71b2e982015fe0464f28da1ab42b8e6375
- Affected versionversion=7960f18a56475bf2177c5ff56c72eb4c12c56440 <1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce
- Affected versionversion=7960f18a56475bf2177c5ff56c72eb4c12c56440 <5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b
- Affected versionversion=7960f18a56475bf2177c5ff56c72eb4c12c56440 <6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f
- Affected versionversion=7960f18a56475bf2177c5ff56c72eb4c12c56440 <7291af9a738d936c2d6869d030711dceb68404d0
- Affected versionversion=7960f18a56475bf2177c5ff56c72eb4c12c56440 <b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65f
- Affected versionversion=7960f18a56475bf2177c5ff56c72eb4c12c56440 <cbb7d8a4b4beb3061b3a1847a742983a01dca381
- Affected versionversion=7960f18a56475bf2177c5ff56c72eb4c12c56440 <f53ab5a2bf20fed59a2f7542d3453228b8056358
What conditions does exploitation require?
What is affected?
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