LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53611: ipmi_si: fix a memleak in try_smi_init()

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in the IPMI system interface driver. It occurs during a failed initialization path after memory is allocated but before cleanup handlers are registered. The source does not indicate remote access, privilege escalation, data theft, or active exploitation.

Executive priority

Treat as routine kernel hygiene unless IPMI is widely used on critical infrastructure. There is no cited exploitation, no CVSS score, and the described impact is a memory leak on an initialization error path.

Technical view

In ipmi_si try_smi_init(), an error before handler registration could leave new_smi->si_sm allocated. The upstream fix adds kfree() in that error path. Affected entries include Linux kernel versions from 4.18 through listed stable series before fixes; severity and CVSS are not provided.

Likely exposure

Most relevant to Linux systems that load or depend on the ipmi_si driver for IPMI/BMC management. Exposure is likely lower for systems without IPMI hardware, without the module loaded, or using vendor kernels already carrying the stable fixes.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The available evidence describes a kernel memory leak found by Kmemleak during module initialization error handling, not a complete attacker path.

Researcher notes

The source evidence is narrow: it identifies the leaking allocation and cleanup fix, but does not define exploit prerequisites, attacker privileges, or practical impact. Avoid overstating risk without distro advisories or additional kernel analysis.

Mitigation direction

  • Apply vendor kernel updates that include the upstream stable fixes.
  • Check Linux distribution advisories for CVE-2023-53611 package status.
  • If IPMI is unnecessary, review vendor-supported options to avoid loading ipmi_si.
  • Prioritize systems using IPMI for server or BMC management.
  • Track reboot requirements after kernel package updates.

Validation and detection

  • Inventory running Linux kernel versions against vendor fixed package data.
  • Check whether ipmi_si is configured, loaded, or operationally required.
  • Confirm the kernel package includes one of the referenced stable fixes.
  • Review vendor changelogs for CVE-2023-53611 or the ipmi_si fix.
  • Monitor for recurring kernel memory leak reports if Kmemleak is enabled.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53611 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7960f18a56475bf2177c5ff56c72eb4c12c56440, 7960f18a56475bf2177c5ff56c72eb4c12c56440, 7960f18a56475bf2177c5ff56c72eb4c12c56440, 7960f18a56475bf2177c5ff56c72eb4c12c56440, 7960f18a56475bf2177c5ff56c72eb4c12c56440, 7960f18a56475bf2177c5ff56c72eb4c12c56440, 7960f18a56475bf2177c5ff56c72eb4c12c56440, 7960f18a56475bf2177c5ff56c72eb4c12c56440unaffected
LinuxLinux4.18, 0, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.53, 6.4.16, 6.5.3, 6.6affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.