High [CVE-2026-85506] Arbitrary code execution via stack-based buffer overflow in ipmi-oem
This high-severity Red Hat Linux advisory covers CVE-2026-85506 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in FreeIPMI. This vulnerability, a stack-based buffer overflow in the `ipmi-oem` component, specifically within the `_get_dell_system_info_idrac_info` function, could allow an attacker to achieve arbitrary code execution.
This occurs when processing the `idrac-info` subcommand to `dell get-system-info`. Exploitation requires a local user to execute a specially crafted `ipmi-oem` command, potentially when processing untrusted data from a remote source, resulting in a complete compromise of the system running FreeIPMI.
Red Hat severity: Important — CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Weakness: CWE-121.
Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9. Red Hat does not currently list a fixing RHSA for this CVE.
Affected products named by the advisory: Red Hat package: freeipmi.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- To mitigate this vulnerability, implement robust boundary checks before copying data to ensure the input size does not exceed the allocated stack buffer capacity. Developers should replace unsafe, unbounded memory functions (like strcpy or sprintf) with safe, length-restricted alternatives (such as strncpy or snprintf). Furthermore, deploying the application in environments that enforce compiler-based protections like stack canaries and Address Space Layout Randomization (ASLR) will prevent successful code execution
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.