CVE-2023-53611

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipmi_si: fix a memleak in try_smi_init()<br /> <br /> Kmemleak reported the following leak info in try_smi_init():<br /> <br /> unreferenced object 0xffff00018ecf9400 (size 1024):<br /> comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s)<br /> backtrace:<br /> [] __kmalloc+0x4b8/0x7b0<br /> [] try_smi_init+0x148/0x5dc [ipmi_si]<br /> [] 0xffff800081b10148<br /> [] do_one_initcall+0x64/0x2a4<br /> [] do_init_module+0x50/0x300<br /> [] load_module+0x7a8/0x9e0<br /> [] __se_sys_init_module+0x104/0x180<br /> [] __arm64_sys_init_module+0x24/0x30<br /> [] el0_svc_common.constprop.0+0x94/0x250<br /> [] do_el0_svc+0x48/0xe0<br /> [] el0_svc+0x24/0x3c<br /> [] el0_sync_handler+0x160/0x164<br /> [] el0_sync+0x160/0x180<br /> <br /> The problem was that when an error occurred before handlers registration<br /> and after allocating `new_smi-&gt;si_sm`, the variable wouldn&amp;#39;t be freed in<br /> the error handling afterwards since `shutdown_smi()` hadn&amp;#39;t been<br /> registered yet. Fix it by adding a `kfree()` in the error handling path<br /> in `try_smi_init()`.