CVE-2023-53611

ipmi_si: fix a memleak in try_smi_init()

MEDIUM
5.5
CVSS Score
Published: October 4, 2025 at 03:44 PM UTC
Updated: June 17, 2026 at 06:45 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

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()`.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.18 ≤ v < 4.19.2954.18 ≤ v < 5.10.1954.18 ≤ v < 5.15.1324.18 ≤ v < 5.4.2574.18 ≤ v < 6.1.534.18 ≤ v < 6.4.164.18 ≤ v < 6.5.34.18 ≤ v < 6.64.20 ≤ v < 5.4.2575.11 ≤ v < 5.15.1325.16 ≤ v < 6.1.535.5 ≤ v < 5.10.1956.2 ≤ v < 6.4.166.5 ≤ v < 6.5.34.187960f18a56475bf2177c5ff56c72eb4c12c56440
Vendor states this is fixed in 09cb2a71b2e982015fe0464f28da1ab42b8e6375 (fixed)
Vendor states this is fixed in 1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce (fixed)
Vendor states this is fixed in 5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b (fixed)
Vendor states this is fixed in 6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f (fixed)
Vendor states this is fixed in 7291af9a738d936c2d6869d030711dceb68404d0 (fixed)
Vendor states this is fixed in b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65f (fixed)
Vendor states this is fixed in cbb7d8a4b4beb3061b3a1847a742983a01dca381 (fixed)
Vendor states this is fixed in f53ab5a2bf20fed59a2f7542d3453228b8056358 (fixed)
Vendor states this is fixed in 4.18 (unaffected)
Vendor states this is fixed in 4.19.295 (unaffected)
Vendor states this is fixed in 5.10.195 (unaffected)
Vendor states this is fixed in 5.15.132 (unaffected)
Vendor states this is fixed in 5.4.257 (unaffected)
Vendor states this is fixed in 6.1.53 (unaffected)
Vendor states this is fixed in 6.4.16 (unaffected)
Vendor states this is fixed in 6.5.3 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-401

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card