LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54064: ipmi:ssif: Fix a memory leak when scanning for an adapter

In the Linux kernel, the following vulnerability has been resolved: ipmi:ssif: Fix a memory leak when scanning for an adapter The adapter scan ssif_info_find() sets info->adapter_name if the adapter info came from SMBIOS, as it's not set in that case. However, this function can be called more than once, and it will leak the adapter name if it had already been set. So check for NULL before setting it.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel memory leak in the IPMI SSIF driver during adapter scanning. Repeated scans can leak the stored adapter name when SMBIOS supplies adapter information. The source does not provide CVSS, severity, exploitability, or business-impact evidence.

Executive priority

Track and remediate through normal kernel patch management. Escalate only for fleets with heavy IPMI SSIF use or strict availability requirements, because severity and exploitation evidence are not provided.

Technical view

In ssif_info_find(), info->adapter_name may be assigned during SMBIOS-derived adapter discovery. If the function runs again after adapter_name is already set, the prior allocation is leaked. The fix checks whether adapter_name is NULL before assigning it.

Likely exposure

Exposure appears limited to Linux systems using the kernel IPMI SSIF path, especially server platforms where SMBIOS-provided IPMI adapter details are relevant. The bundle lists affected Linux kernel versions and stable fix commits, but no deployment prevalence.

Exploitation context

No active exploitation is cited. The CVE is not marked KEV, and the supplied sources do not describe exploit prerequisites, attacker reachability, or a weaponized technique. Treat exploitation status as unproven.

Researcher notes

The evidence supports a bounded kernel memory leak in IPMI SSIF adapter discovery. Missing data includes CVSS, CWE, exploitability, reachable attack surface, and exact distribution package status. Avoid assuming remote exploitability from the provided sources.

Mitigation direction

  • Identify systems using affected Linux kernel versions and the IPMI SSIF driver.
  • Apply the relevant vendor or upstream stable kernel update containing the fix.
  • Prioritize servers using IPMI management interfaces or SMBIOS-discovered adapters.
  • Check Linux distribution advisories for packaged kernel fix availability.

Validation and detection

  • Compare deployed kernel versions against the CVE affected-version data and stable fix references.
  • Confirm whether IPMI SSIF support is present on in-scope server platforms.
  • Review vendor kernel changelogs for the referenced adapter_name leak fix.
  • Monitor system memory behavior only as supporting evidence, not proof of vulnerability.
Prepared
Confidence
medium
Sources
9

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-54064 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
8Source 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
LinuxLinuxc4436c9149c5d2bc0c49ab57ec85c75ea1c4d61c, c4436c9149c5d2bc0c49ab57ec85c75ea1c4d61c, c4436c9149c5d2bc0c49ab57ec85c75ea1c4d61c, c4436c9149c5d2bc0c49ab57ec85c75ea1c4d61c, c4436c9149c5d2bc0c49ab57ec85c75ea1c4d61c, c4436c9149c5d2bc0c49ab57ec85c75ea1c4d61c, c4436c9149c5d2bc0c49ab57ec85c75ea1c4d61cunaffected
LinuxLinux5.4, 0, 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.