The Linux kernel's lockd module improperly handles allocation failure of a lockowner in nlmclnt_locks_init_private(). When nlmclnt_find_lockowner() fails to allocate a lockowner, nlmclnt_proc() returns -ENOMEM, but the VFS proceeds to tear down a partially initialized file_lock and calls locks_release_private(). This triggers nlmclnt_locks_release_private(), which dereferences the uninitialized fl->fl_u.nfs_fl.owner pointer, causing a NULL pointer dereference and kernel crash. The fix involves clearing fl_ops before initializing the NLM private state and only installing NLM lock operations after successful lockowner allocation.

This vulnerability can cause a kernel crash (NULL pointer dereference) when the lockowner allocation fails, potentially leading to denial of service on affected systems. There is no indication of code execution or privilege escalation from the provided data.

A fix has been implemented in the Linux kernel to address this issue by ensuring lock operations are only installed after successful lockowner allocation. Users should apply the official kernel updates that include this fix. Patch status is not explicitly stated in the provided data; check the vendor advisory for current remediation guidance.