CVE-2026-89495
Linux · Kernel
The Linux kernel OCFS2 DLM component fails to validate length fields in network messages, leading to heap out-of-bounds memory corruption or system panics.
Executive summary
A critical vulnerability in the Linux kernel OCFS2 Distributed Lock Manager allows remote, unauthenticated attackers to cause memory corruption or a kernel panic.
Vulnerability
The o2dlm subsystem processes network messages without verifying length and count fields, leading to multiple heap out-of-bounds write vulnerabilities and an out-of-bounds read that triggers a system panic. This flaw is reachable by an unauthenticated node within the same DLM domain.
Business impact
Successful exploitation of this vulnerability can lead to a complete system crash, resulting in significant denial of service for critical infrastructure relying on OCFS2 cluster filesystems. Furthermore, the potential for heap memory corruption creates an opportunity for attackers to manipulate kernel memory, which may lead to unauthorized data access or system compromise. With a CVSS score of 9.8, the severity is critical due to the lack of required authentication and the potential for remote execution of malicious logic within the kernel space.
Remediation
Immediate Action: Update the Linux kernel to version 5.10.270, 5.15.221, 6.1.188, or later, as specified by the stable kernel branch maintainers.
Proactive Monitoring: Monitor system logs for unexpected kernel panics or BUG_ON messages related to the o2dlm subsystem.
Compensating Controls: Restrict network access to the cluster interconnect to trusted nodes only, ensuring that only authorized traffic can interact with the OCFS2 DLM communication channels.
Exploitation status
Public Exploit Available: Unknown.
Analyst recommendation
Given the critical nature of kernel-level memory corruption, administrators operating OCFS2 clusters must prioritize patching their environments. The vulnerability allows for high-impact disruption, and immediate application of the provided stable kernel updates is the only definitive way to mitigate this risk.
More Linux CVEs all →
History
CVE Brief tracked this CVE 5 days before it had a CVSS score.
- Disclosed CVE record published
- Collected by CVE Brief No CVSS score yet; tracked as early warning
- CVSS score assigned 9.8 (3.1)
- Analyst report written