Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 09cb2a71b2e982015fe0464f28da1ab42b8e6375, 1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce, 5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b.

Low priority for now. Upgrade to Linux Linux 09cb2a71b2e982015fe0464f28da1ab42b8e6375, 1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ce, 5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26b or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 4, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53611

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.18 and later · before 4.19.295
  • linux linux kernel4.20 and later · before 5.4.257
  • linux linux kernel5.5 and later · before 5.10.195
  • linux linux kernel5.11 and later · before 5.15.132
  • linux linux kernel5.16 and later · before 6.1.53
  • linux linux kernel6.2 and later · before 6.4.16
  • linux linux kernel6.5 and later · before 6.5.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.18affected
    • 7960f18a56475bf2177c5ff56c72eb4c12c56440 and later · before b9bc8fbb2d416ce87f0342478dc9fcfd79f2c65faffected · git
    • 7960f18a56475bf2177c5ff56c72eb4c12c56440 and later · before f53ab5a2bf20fed59a2f7542d3453228b8056358affected · git
    • 7960f18a56475bf2177c5ff56c72eb4c12c56440 and later · before 5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26baffected · git
    • 7960f18a56475bf2177c5ff56c72eb4c12c56440 and later · before cbb7d8a4b4beb3061b3a1847a742983a01dca381affected · git
    • 7960f18a56475bf2177c5ff56c72eb4c12c56440 and later · before 09cb2a71b2e982015fe0464f28da1ab42b8e6375affected · git
    • 7960f18a56475bf2177c5ff56c72eb4c12c56440 and later · before 1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ceaffected · git
    • 7960f18a56475bf2177c5ff56c72eb4c12c56440 and later · before 7291af9a738d936c2d6869d030711dceb68404d0affected · git
    • 7960f18a56475bf2177c5ff56c72eb4c12c56440 and later · before 6cf1a126de2992b4efe1c3c4d398f8de4aed6e3faffected · git
    • before 4.18not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.55-16.1.55-1
Debian:13linuxbefore 6.5.3-16.5.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53599Oct 4, 2025 · crypto: af_alg - Fix missing initialisation affecting gcm-aes-s390
    22Monitor
  • ← EarlierCVE-2023-53608Oct 4, 2025 · nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread()
    31Monitor
  • Later →CVE-2023-53613Oct 4, 2025 · dax: Fix dax_mapping_release() use after free
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux09cb2a71b2e982015fe0464f28da1ab42b8e6375Vendor (CNA)
Linux Linux1bfcfea0fae0d0a6c6ff5543e6d704b3807b83ceVendor (CNA)
Linux Linux5c5f02e16b919c8cb6024dc3778c8d8f1fb1f26bVendor (CNA)
Linux Linux6cf1a126de2992b4efe1c3c4d398f8de4aed6e3fVendor (CNA)
Linux Linux7291af9a738d936c2d6869d030711dceb68404d0Vendor (CNA)
Linux Linuxb9bc8fbb2d416ce87f0342478dc9fcfd79f2c65fVendor (CNA)
Linux Linuxcbb7d8a4b4beb3061b3a1847a742983a01dca381Vendor (CNA)
Linux Linuxf53ab5a2bf20fed59a2f7542d3453228b8056358Vendor (CNA)
debian:linux6.1.55-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records