This kernel defect arises in the OCFS2 cluster heartbeat subsystem. When a local node is stopped, internal flags are not cleared, leaving an invalid node identifier (255) in the shared state. Heartbeat threads that later read this stale value trigger out‑of‑bounds memory accesses, as evidenced by KASAN reports, and can cause a kernel crash. The flaw is a classic memory corruption vulnerability that could lead to privileged code execution if an attacker can influence the OCFS2 heartbeat process.

The vulnerability affects the Linux kernel, specifically the OCFS2/cluster implementation. No specific version list is supplied, so any kernel containing the described stale heartbeat logic may be impacted until the upstream patch is applied. Systems running OCFS2 clusters should evaluate their kernel versions for this condition.

Although the EPSS score is very low (<1%) and the issue is not listed in the KEV catalog, kernel memory corruption is inherently high severity in CVSS terms. Exploitation would require the ability to control the OCFS2 heartbeat state, likely by starting and stopping nodes in a particular sequence. The absence of a public exploit yet does not reduce the importance of patching, as the failure mode can destabilize the entire system.