PT-2026-90200 · Linux · Linux
CVE-2026-89484
·
Published
2026-09-11
·
Updated
2026-09-11
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux