CVE-2026-89484 Linux CVE debrief

Who should care

Linux kernel maintainers, Linux distribution maintainers, and users of Linux kernel-based systems should assess exposure and verify patch deployment to prevent system crashes due to NULL dereference in lockd. Linux kernel users and maintainers should assess exposure and verify patch deployment.

Why it matters

Linux kernel users and maintainers should assess exposure and verify patch deployment to prevent system crashes due to NULL dereference in lockd.

• crash on lockowner allocation failure
• NULL dereference in nlmclnt_locks_release_private()

Technical summary

The Linux kernel's lockd subsystem is vulnerable to a NULL dereference when lockowner allocation fails. This occurs because nlmclnt_locks_init_private() installs NLM file lock operations before a lockowner is successfully allocated. When nlmclnt_proc() returns -ENOMEM, the VFS still attempts to clean up the partially initialized file_lock, leading to a crash in nlmclnt_locks_release_private(). The issue arises when nlmclnt_locks_init_private() installs NLM file lock operations even if nlmclnt_find_lockowner() fails to allocate a lockowner. Subsequently, nlmclnt_proc() returns -ENOMEM, but the VFS still attempts to tear down the partially initialized file_lock, leading to a call to locks_release_private().

Defensive priority

Linux kernel maintainers and users should assess exposure and verify patch deployment.

Recommended defensive actions

• Review Linux kernel patch deployment for the fix.
• Assess exposure in Linux kernel-based systems.
• Verify system crash handling and monitoring.
• 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 CVE record and NVD entry provide details on the vulnerability in the Linux kernel's lockd subsystem, which is vulnerable to a NULL dereference when lockowner allocation fails. This occurs because nlmclnt_locks_init_private() installs NLM file lock operations before a lockowner is successfully allocated. When nlmclnt_proc() returns -ENOMEM, the VFS still attempts to clean up the partially initialized file_lock, leading to a crash in nlmclnt_locks_release_private(). Linux kernel users and maintainers should assess exposure and to

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.