CVE-2023-53611
- Published: 2025-10-04T16:15:57.863
In the Linux kernel, the following vulnerability has been resolved:
ipmi_si: fix a memleak in try_smi_init()
Kmemleak reported the following leak info in try_smi_init():
unreferenced object 0xffff00018ecf9400 (size 1024):
comm “modprobe”, pid 2707763, jiffies 4300851415 (age 773.308s)
backtrace:
[] __kmalloc+0x4b8/0x7b0
[] try_smi_init+0x148/0x5dc [ipmi_si]
[] 0xffff800081b10148
[] do_one_initcall+0x64/0x2a4
[] do_init_module+0x50/0x300
[] load_module+0x7a8/0x9e0
[] __se_sys_init_module+0x104/0x180
[] __arm64_sys_init_module+0x24/0x30
[] el0_svc_common.constprop.0+0x94/0x250
[] do_el0_svc+0x48/0xe0
[] el0_svc+0x24/0x3c
[] el0_sync_handler+0x160/0x164
[] el0_sync+0x160/0x180
The problem was that when an error occurred before handlers registration
and after allocating `new_smi->si_sm`, the variable wouldn’t be freed in
the error handling afterwards since `shutdown_smi()` hadn’t been
registered yet. Fix it by adding a `kfree()` in the error handling path
in `try_smi_init()`.
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
No vendor taxonomy on this entry.
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2023-53611
Description: In the Linux kernel, the following vulnerability has been resolved: ipmi_si: fix a memleak in try_smi_init() Kmemleak reported the following leak info in try_smi_init(): unreferenced object 0xffff00018ecf9400 (size 1024): comm “modprobe”, pid 2707763, jiffies 4300851415 (age 773.308s) backtrace: [] __kmalloc+0x4b8/0x7b0 [] try_smi_init+0x148/0x5dc [ipmi_si] [] 0xffff800081b10148 [] do_one_initcall+0x64/0x2a4 [] do_init_module+0x50/0x300 [] load_module+0x7a8/0x9e0 [] __se_sys_init_module+0x104/0x180 [] __arm64_sys_init_module+0x24/0x30 […]
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
- Check if you're running the affected product
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Exploit Difficulty Assessment
Vulnerability Timeline
CVE details first published to NVD database
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
No vendor/product data available.