CVE-2026-81004

8.4

Linux · Kernel

A race condition or improper cleanup in the Linux kernel IPMI message handler allows for potential memory corruption when an interface startup error occurs.

Executive summary

A vulnerability in the Linux kernel IPMI message handler could allow a local attacker to cause a system crash or potentially achieve arbitrary code execution via improper work cancellation.

Vulnerability

The vulnerability exists within the IPMI message handler component, where scheduled work is not correctly canceled during an interface startup error. This failure to clean up resources before freeing the interface can lead to a use-after-free condition, which is exploitable by a local, unauthenticated user.

Business impact

The exploitation of this kernel-level vulnerability could lead to a complete system compromise, including unauthorized access to sensitive data, privilege escalation, and persistent denial-of-service conditions. With a CVSS score of 8.4, this flaw poses a High severity risk, as successful exploitation results in full loss of Confidentiality, Integrity, and Availability for the host system.

Remediation

Immediate Action: Update your Linux kernel to version 6.18.50, 7.2.4, or a later stable release provided by your distribution vendor.

Proactive Monitoring: Monitor system logs for kernel panic events or unusual IPMI-related error messages that may indicate an exploitation attempt.

Compensating Controls: Restrict access to the IPMI interface and limit user access to the local machine, as this vulnerability requires local access to trigger the flaw.

Exploitation status

Public Exploit Available: No (exploit_available: unknown)

Analyst recommendation

Given the potential for system-wide compromise through kernel-level exploitation, organizations should prioritize patching affected Linux systems as part of their standard maintenance cycle. Ensure that all production servers are updated to the specified patched versions to eliminate the underlying memory management flaw.

More Linux CVEs all →

History

CVE Brief tracked this CVE 1 day before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 8.4 (3.1)
  4. Analyst report written
  5. Published in the daily brief high section

Sources