CVE-2026-85504: FreeIPMI before 1.6.19 has a stack-based buffer overflow in _ipmi_sel_oem_fujitsu_get_sel_entry_long_text i...
FreeIPMI before 1.6.19 has a stack-based buffer overflow in _ipmi_sel_oem_fujitsu_get_sel_entry_long_text in libfreeipmi/sel/ipmi-sel-string-fujitsu-irmc-common.c via malformed Fujitsu SEL long-text responses.
Security readout for executives and security teams
Plain-English summary
FreeIPMI versions before 1.6.19 can overflow memory while processing a malformed Fujitsu iRMC system-event-log long-text response. A successful attack could potentially crash the affected process or compromise confidentiality and integrity. Risk depends on whether vulnerable FreeIPMI code processes attacker-influenced Fujitsu SEL responses.
Executive priority
Treat as an urgent patching and exposure-review item because the reported impact is critical and requires no privileges or user interaction. Prioritize reachable management systems and Fujitsu iRMC integrations. There is no supplied evidence of active exploitation, so urgency should reflect exposure rather than an assumed ongoing campaign.
Technical view
The flaw is a stack-based buffer overflow (CWE-121) in _ipmi_sel_oem_fujitsu_get_sel_entry_long_text within libfreeipmi. It is triggered by malformed Fujitsu SEL long-text responses. The supplied CVSS 3.1 score is 9.8, with network reachability, low complexity, no privileges, and no user interaction represented in the vector.
Likely exposure
Systems running FreeIPMI earlier than 1.6.19 are potentially affected when they process Fujitsu iRMC SEL long-text responses. The supplied evidence does not identify affected operating-system packages, default deployment paths, or whether every FreeIPMI installation invokes the vulnerable function.
Exploitation context
The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. The CVSS vector indicates potentially remote exploitation, but practical reachability depends on whether an attacker can supply or influence the Fujitsu SEL response consumed by FreeIPMI.
Researcher notes
The supplied record identifies the vulnerable function, source file, malformed-response trigger, CWE-121 classification, and fixed-version boundary. It does not establish the vulnerable buffer dimensions, affected call paths, package backports, exploit reliability, or observed attacks. Validate vendor patches and deployment reachability without assuming the CVSS network vector means direct Internet exposure.
Mitigation direction
Upgrade FreeIPMI to version 1.6.19 or a vendor-packaged release containing the correction.
Check operating-system and appliance vendor advisories for package-specific remediation guidance.
Until updated, restrict affected management workflows from untrusted or attacker-controlled response sources.
Prioritize systems where FreeIPMI communicates with Fujitsu iRMC interfaces across exposed or untrusted networks.
Validation and detection
Inventory FreeIPMI versions across hosts, appliances, containers, and management tooling.
Confirm installed packages are version 1.6.19 or vendor-confirmed fixed builds.
Identify workflows that retrieve or parse Fujitsu iRMC SEL long-text responses.
Review process crashes and memory-fault telemetry involving FreeIPMI SEL handling.
Verify network controls limit relevant management traffic to trusted systems.
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.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.