CVE-2023-53611

MEDIUM EPSS 3.2%
Published Oct 4, 20258mo ago · Modified Jun 17, 20261w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Oct 4, 2025 8mo ago
Last Modified Jun 17, 2026 1w ago

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

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
3.2% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-401

Affected Products 7

VendorProductVersionRange
linuxlinux_kernel*≥4.18  –  <4.19.295
linuxlinux_kernel*≥4.20  –  <5.4.257
linuxlinux_kernel*≥5.5  –  <5.10.195
linuxlinux_kernel*≥5.11  –  <5.15.132
linuxlinux_kernel*≥5.16  –  <6.1.53
linuxlinux_kernel*≥6.2  –  <6.4.16
linuxlinux_kernel*≥6.5  –  <6.5.3

References 8

  • git.kernel.org https://git.kernel.org/stable/c/09cb2a71b2e982015fe0464f28da1ab42b8e6375
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/7291af9a738d936c2d6869d030711dceb68404d0
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65f
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/cbb7d8a4b4beb3061b3a1847a742983a01dca381
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f53ab5a2bf20fed59a2f7542d3453228b8056358
    Patch

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/09cb2a71b2e982015fe0464f28da1ab42b8e6375
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/6cf1a126de2992b4efe1c3c4d398f8de4aed6e3f
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/7291af9a738d936c2d6869d030711dceb68404d0
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65f
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/cbb7d8a4b4beb3061b3a1847a742983a01dca381
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f53ab5a2bf20fed59a2f7542d3453228b8056358
    Patch