linux-cve-announce - CVE-2023-53611: ipmi_si: fix a memleak in try_smi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100433-CVE-2023-53611-a508@gregkh>
Date: Sat,  4 Oct 2025 17:52:05 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53611: ipmi_si: fix a memleak in try_smi_init()

From: Greg Kroah-Hartman <gregkh@...nel.org>

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:
    [<000000004ca5b312>] __kmalloc+0x4b8/0x7b0
    [<00000000953b1072>] try_smi_init+0x148/0x5dc [ipmi_si]
    [<000000006460d325>] 0xffff800081b10148
    [<0000000039206ea5>] do_one_initcall+0x64/0x2a4
    [<00000000601399ce>] do_init_module+0x50/0x300
    [<000000003c12ba3c>] load_module+0x7a8/0x9e0
    [<00000000c246fffe>] __se_sys_init_module+0x104/0x180
    [<00000000eea99093>] __arm64_sys_init_module+0x24/0x30
    [<0000000021b1ef87>] el0_svc_common.constprop.0+0x94/0x250
    [<0000000070f4f8b7>] do_el0_svc+0x48/0xe0
    [<000000005a05337f>] el0_svc+0x24/0x3c
    [<000000005eb248d6>] el0_sync_handler+0x160/0x164
    [<0000000030a59039>] 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()`.

The Linux kernel CVE team has assigned CVE-2023-53611 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.18 with commit 7960f18a56475bf2177c5ff56c72eb4c12c56440 and fixed in 4.19.295 with commit b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65f
	Issue introduced in 4.18 with commit 7960f18a56475bf2177c5ff56c72eb4c12c56440 and fixed in 5.4.257 with commit f53ab5a2bf20fed59a2f7542d3453228b8056358
	Issue introduced in 4.18 with commit 7960f18a56475bf2177c5ff56c72eb4c12c56440 and fixed in 5.10.195 with commit 5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b
	Issue introduced in 4.18 with commit 7960f18a56475bf2177c5ff56c72eb4c12c56440 and fixed in 5.15.132 with commit cbb7d8a4b4beb3061b3a1847a742983a01dca381
	Issue introduced in 4.18 with commit 7960f18a56475bf2177c5ff56c72eb4c12c56440 and fixed in 6.1.53 with commit 09cb2a71b2e982015fe0464f28da1ab42b8e6375
	Issue introduced in 4.18 with commit 7960f18a56475bf2177c5ff56c72eb4c12c56440 and fixed in 6.4.16 with commit 1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce
	Issue introduced in 4.18 with commit 7960f18a56475bf2177c5ff56c72eb4c12c56440 and fixed in 6.5.3 with commit 7291af9a738d936c2d6869d030711dceb68404d0
	Issue introduced in 4.18 with commit 7960f18a56475bf2177c5ff56c72eb4c12c56440 and fixed in 6.6 with commit 6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53611
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/char/ipmi/ipmi_si_intf.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65f
	https://git.kernel.org/stable/c/f53ab5a2bf20fed59a2f7542d3453228b8056358
	https://git.kernel.org/stable/c/5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b
	https://git.kernel.org/stable/c/cbb7d8a4b4beb3061b3a1847a742983a01dca381
	https://git.kernel.org/stable/c/09cb2a71b2e982015fe0464f28da1ab42b8e6375
	https://git.kernel.org/stable/c/1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce
	https://git.kernel.org/stable/c/7291af9a738d936c2d6869d030711dceb68404d0
	https://git.kernel.org/stable/c/6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f