CVE-2023-53611
published 2025-10-04CVE-2023-53611: 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…
PriorityP416medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.14%
3.4th percentile
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()`.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.55-1 (bookworm) | linux 6.1.55-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 7960f18a56475bf2177c5ff56c72eb4c12c56440 < b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65f | b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65f |
| linux | linux | >= 7960f18a56475bf2177c5ff56c72eb4c12c56440 < f53ab5a2bf20fed59a2f7542d3453228b8056358 | f53ab5a2bf20fed59a2f7542d3453228b8056358 |
| linux | linux | >= 7960f18a56475bf2177c5ff56c72eb4c12c56440 < 5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b | 5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b |
| linux | linux | >= 7960f18a56475bf2177c5ff56c72eb4c12c56440 < cbb7d8a4b4beb3061b3a1847a742983a01dca381 | cbb7d8a4b4beb3061b3a1847a742983a01dca381 |
| linux | linux | >= 7960f18a56475bf2177c5ff56c72eb4c12c56440 < 09cb2a71b2e982015fe0464f28da1ab42b8e6375 | 09cb2a71b2e982015fe0464f28da1ab42b8e6375 |
| linux | linux | >= 7960f18a56475bf2177c5ff56c72eb4c12c56440 < 1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce | 1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce |
| linux | linux | >= 7960f18a56475bf2177c5ff56c72eb4c12c56440 < 7291af9a738d936c2d6869d030711dceb68404d0 | 7291af9a738d936c2d6869d030711dceb68404d0 |
| linux | linux | >= 7960f18a56475bf2177c5ff56c72eb4c12c56440 < 6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f | 6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f |
| linux | linux_kernel | >= 0 < 5.10.197-1 | 5.10.197-1 |
| linux | linux_kernel | >= 0 < 6.1.55-1 | 6.1.55-1 |
| linux | linux_kernel | >= 0 < 6.5.3-1 | 6.5.3-1 |
| linux | linux_kernel | >= 0 < 6.5.3-1 | 6.5.3-1 |
| linux | linux_kernel | >= 4.18 < 4.19.295 | 4.19.295 |
| linux | linux_kernel | >= 4.20 < 5.4.257 | 5.4.257 |
| linux | linux_kernel | >= 5.11 < 5.15.132 | 5.15.132 |
| linux | linux_kernel | >= 5.16 < 6.1.53 | 6.1.53 |
| linux | linux_kernel | >= 5.5 < 5.10.195 | 5.10.195 |
| linux | linux_kernel | >= 6.2 < 6.4.16 | 6.4.16 |
| linux | linux_kernel | >= 6.5 < 6.5.3 | 6.5.3 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: ipmi_si: fix a memleak in try_smi_init()
vendor_redhat·2025-10-04·CVSS 5.5
CVE-2023-53611 [MEDIUM] CWE-771 kernel: ipmi_si: fix a memleak in try_smi_init()
kernel: ipmi_si: fix a memleak in try_smi_init()
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 registr
Debian
CVE-2023-53611: linux - In the Linux kernel, the following vulnerability has been resolved: ipmi_si: fi...
vendor_debian·2023·CVSS 5.5
CVE-2023-53611 [MEDIUM] CVE-2023-53611: linux - In the Linux kernel, the following vulnerability has been resolved: ipmi_si: fi...
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 v
VulDB
Linux Kernel up to 6.5.2 ipmi_si try_smi_init memory leak (EUVD-2023-59997 / Nessus ID 278484)
vuldb·2026-04-28·CVSS 5.5
CVE-2023-53611 [MEDIUM] Linux Kernel up to 6.5.2 ipmi_si try_smi_init memory leak (EUVD-2023-59997 / Nessus ID 278484)
A vulnerability labeled as critical has been found in Linux Kernel up to 6.5.2. Affected by this vulnerability is the function try_smi_init of the component ipmi_si. The manipulation results in memory leak.
This vulnerability is reported as CVE-2023-53611. The attacker must have access to the local network to execute the attack. No exploit exists.
The affected component should be upgraded.
GHSA
GHSA-7r62-fw3j-xjqf: In the Linux kernel, the following vulnerability has been resolved:
ipmi_si: fix a memleak in try_smi_init()
Kmemleak reported the following leak in
ghsa_unreviewed·2025-10-04
CVE-2023-53611 [MEDIUM] CWE-401 GHSA-7r62-fw3j-xjqf: In the Linux kernel, the following vulnerability has been resolved:
ipmi_si: fix a memleak in try_smi_init()
Kmemleak reported the following leak in
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`, t
OSV
CVE-2023-53611: 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
osv·2025-10-04·CVSS 5.5
CVE-2023-53611 [MEDIUM] CVE-2023-53611: 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 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 v
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/09cb2a71b2e982015fe0464f28da1ab42b8e6375https://git.kernel.org/stable/c/1bfcfea0fae0d0a6c6ff5543e6d704b3807b83cehttps://git.kernel.org/stable/c/5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26bhttps://git.kernel.org/stable/c/6cf1a126de2992b4efe1c3c4d398f8de4aed6e3fhttps://git.kernel.org/stable/c/7291af9a738d936c2d6869d030711dceb68404d0https://git.kernel.org/stable/c/b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65fhttps://git.kernel.org/stable/c/cbb7d8a4b4beb3061b3a1847a742983a01dca381https://git.kernel.org/stable/c/f53ab5a2bf20fed59a2f7542d3453228b8056358
2025-10-04
Published