CVE-2023-53611: ipmi_si: fix a memleak in try_smi_init()
In the Linux kernel, the following vulnerability has been resolved:
ipmisi: fix a memleak in trysmiinit()
Kmemleak reported the following leak info in trysmiinit():
unreferenced object 0xffff00018ecf9400 (size 1024): comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s) backtrace: [<000000004ca5b312>] kmalloc+0x4b8/0x7b0 [<00000000953b1072>] trysmiinit+0x148/0x5dc [ipmisi] [<000000006460d325>] 0xffff800081b10148 [<0000000039206ea5>] dooneinitcall+0x64/0x2a4 [<00000000601399ce>] doinitmodule+0x50/0x300 [<000000003c12ba3c>] loadmodule+0x7a8/0x9e0 [<00000000c246fffe>] sesysinitmodule+0x104/0x180 [<00000000eea99093>] arm64sysinitmodule+0x24/0x30 [<0000000021b1ef87>] el0svccommon.constprop.0+0x94/0x250 [<0000000070f4f8b7>] doel0svc+0x48/0xe0 [<000000005a05337f>] el0svc+0x24/0x3c [<000000005eb248d6>] el0synchandler+0x160/0x164 [<0000000030a59039>] el0sync+0x160/0x180
The problem was that when an error occurred before handlers registration and after allocating newsmi->sism, the variable wouldn't be freed in the error handling afterwards since shutdownsmi() hadn't been registered yet. Fix it by adding a kfree() in the error handling path in trysmiinit().
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-53611?
CVE-2023-53611 has been classified as a moderate severity vulnerability.
How do I fix CVE-2023-53611?
To fix CVE-2023-53611, update the Linux kernel to the latest version that includes the patch for this vulnerability.
What is the main issue caused by CVE-2023-53611?
CVE-2023-53611 addresses a memory leak in the 'try_smi_init()' function within the Linux kernel.
Which versions of the Linux kernel are affected by CVE-2023-53611?
CVE-2023-53611 affects various versions of the Linux kernel prior to the application of the relevant patch.
Can CVE-2023-53611 lead to system instability?
Yes, CVE-2023-53611 can potentially lead to system instability due to resource leaks.