Description
In the Linux kernel, the following vulnerability has been resolved:
lockd: fix NULL dereference on lockowner allocation failure
nlmclnt_locks_init_private() installs NLM file lock operations even when nlmclnt_find_lockowner() fails to allocate a lockowner. nlmclnt_proc() then returns -ENOMEM, but the VFS still tears down the partially initialized file_lock and calls locks_release_private().
That invokes nlmclnt_locks_release_private(), which dereferences fl->fl_u.nfs_fl.owner and crashes because the owner was never installed.
Clear fl_ops before attempting to initialize the NLM private state, and install the NLM lock operations only after a lockowner has been allocated successfully.
Metrics
No CVSS score has been published yet.
Affected software
Source: the vendor's advisory (CNA). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < b61053a3795c2913a7af3ab6218acfdaf52fcafe; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 6db5af172ccc3223c8f730a9a4212f6427feee3e; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 07adfbb3de7529f58ca708a97ead7fa4fdb71056; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d662f7fc04fde305a27f304b3cd19b614d366839; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 51af080ca4e553256c59a75a877b9b4fff828311; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4c7fc129db061c7daab841c4f3c342d894832362 |
| Linux | Linux | 2.6.12 |
References
- https://git.kernel.org/stable/c/07adfbb3de7529f58ca708a97ead7fa4fdb71056
- https://git.kernel.org/stable/c/4c7fc129db061c7daab841c4f3c342d894832362
- https://git.kernel.org/stable/c/51af080ca4e553256c59a75a877b9b4fff828311
- https://git.kernel.org/stable/c/6db5af172ccc3223c8f730a9a4212f6427feee3e
- https://git.kernel.org/stable/c/b61053a3795c2913a7af3ab6218acfdaf52fcafe
- https://git.kernel.org/stable/c/d662f7fc04fde305a27f304b3cd19b614d366839
Timeline
- Published
- Sep 11, 2026
- Last modified
- Oct 30, 2026
- NVD status
- Received