From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A9676583ABD for ; Fri, 11 Sep 2026 19:54:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156454; cv=none; b=OKPuFNwaf1kYHhQXgM6D1rozC6WRfqm/1TdmPDaHw2P42Q9NB64R3BCog9UO5CGLFY6bnw7KwtnayJoaWTkQPq9P7LOL82KOCx5QQcJCv6gYkSeD1ZX2YxovuJbXphe+s+Pnl4ef9adDpCMqEFaTsauZURAPt8N+PQ9XXh7s8ZE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156454; c=relaxed/simple; bh=MXXUdKjjBXXpUhLbOmTylmmXb9KAZ/VFElNlDGjQryc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=NG2bxfOmhma93srLEgS0nFVTuGH4Hnf71oDGuMlB7Tda6YkKbh47Y+wZnRri7ixs4I1OeteReq+y/ELheGQf454sxF075vCCy9y1JFHIhM70aAoxgWOp6bjPd1F3MaIGY77+HbeoVxQ9OPt9taEM87O+pZ4kBtToaNU90FPbKiw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=No8DPEVp; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="No8DPEVp" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A83521F0089C; Fri, 11 Sep 2026 19:54:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156441; bh=rmx2zy0OCGvuLRYnxvDAoy/r8XfKjMeaeNwIpUjLEm4=; h=From:To:Cc:Subject:Date:Reply-To; b=No8DPEVpIl1t5JoX0j9B4Ivr5Wp2I9epLXttl9d57rrg9hfXODjiVHtWwcuolSODl sgn1Gm+QKAAPCKnkY6YiCYdK370lVquHQheDb6DqhdgIGVBE+pgc218p5R/7V4+lVu vDFIvksnIwmpMBjV0HF3upWR/TJMR08cjnjsdBZE= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89484: lockd: fix NULL dereference on lockowner allocation failure Date: Fri, 11 Sep 2026 21:42:53 +0200 Message-ID: <2026091106-CVE-2026-89484-4a52@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2806; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=FkzC16HOAOBzzkgjTT0zIa40q2YF4SC5ik82P6jbez4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIoMOsJX9+K0gsb+M0WKh8MeA6dm5kfN0TmrYOR1/X P/m5f4fHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRp6sY5mdMUlON/LBwEUdB xa+dOh+qlE/uucKwYM6V6P7eM3pyIvv0VI3fztui3Mq4CQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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. The Linux kernel CVE team has assigned CVE-2026-89484 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.109 with commit 07adfbb3de7529f58ca708a97ead7fa4fdb71056 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18.50 with commit d662f7fc04fde305a27f304b3cd19b614d366839 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.2.4 with commit 51af080ca4e553256c59a75a877b9b4fff828311 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.3-rc1 with commit 4c7fc129db061c7daab841c4f3c342d894832362 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-89484 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: fs/lockd/clntproc.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/07adfbb3de7529f58ca708a97ead7fa4fdb71056 https://git.kernel.org/stable/c/d662f7fc04fde305a27f304b3cd19b614d366839 https://git.kernel.org/stable/c/51af080ca4e553256c59a75a877b9b4fff828311 https://git.kernel.org/stable/c/4c7fc129db061c7daab841c4f3c342d894832362