CVE-2026-90322

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

ocfs2/cluster: keep heartbeat local node stable

o2nm_node_local_store() handles local=0 by stopping o2net and setting

cl_local_node to O2NM_INVALID_NODE_NUM, but it leaves cl_has_local set.

That stale state makes o2nm_this_node() return 255, blocks a later local=1

attempt with -EBUSY, and can feed 255 to heartbeat users that call

o2nm_this_node() dynamically.

Clearing cl_has_local is required when the local node is reset. But

heartbeat threads can still be running at that point. They pin the local

node config item at startup, yet o2hb_do_disk_heartbeat() and thread

teardown re-read o2nm_this_node() for the local slot and for

o2nm_undepend_this_node(). Once local=0 has cleared the live local-node

state, those dynamic reads return O2NM_MAX_NODES, which is also the

invalid node number 255.

Store the local node number in the heartbeat region when the region

starts. Use that stable node for heartbeat slot writes/ch

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References