CVE-2026-89495 Linux CVE debrief

Who should care

Defenders managing Linux kernel environments, especially those using DLM domains, should assess exposure and prioritize patching to prevent potential corruption or panic of nodes in the domain.

Why it matters

Defenders managing Linux kernel environments, especially those using DLM domains, should assess exposure and prioritize patching to prevent potential corruption or panic of nodes in the domain.

• Potential corruption or panic of nodes in a DLM domain due to malformed messages.
• Verification priority for Linux kernel versions in use and potential exposure in DLM domain environments.
• Possible malicious activity from compromised or malicious members in the domain.

Technical summary

The o2dlm receive handlers trust u8 length and count fields from the wire without bounding them, allowing a node in a DLM domain to corrupt or panic any other node with a malformed message. Three defects were identified and resolved in a patch series: dlm_migrate_request_handler() passes migrate->namelen unchecked to dlm_init_mle(), dlm_mig_lockres_handler() passes mres->lockname_len unchecked to dlm_init_lockres(), and the same handler trusts mres->num_locks without checking that the message is large enough to hold that many entries.

Defensive priority

Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, especially in DLM domain environments.

Recommended defensive actions

• Verify Linux kernel versions in use and check if they are affected by this vulnerability.
• Apply patches for Linux kernel versions affected by this vulnerability.
• Monitor DLM domain environments for potential malicious activity.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability was confirmed under KASAN with an out-of-tree module mirroring it exactly. Scrubbed logs are available on request. The issue was identified in the o2dlm receive handlers, which trust u8 length and count fields from the wire without bounding them. This allows a node in a DLM domain to corrupt or panic any other node with a malformed message. The patch series resolves three defects: dlm_migrate_request_handler(), dlm_mig_lockres_handler(), and the same handler trusts mres->num_locks without checking that the message is

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.