From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154294; b=DA0BE5pxXCHFW51QGtgx+1YCzg7mBBQdQw4+1LEXKRmoFmH63YdOZ4nM03xawCIZKeff rzr4nxF9aB59Pi/uqk2TUxnJfuvBL0erSZfJmc0XOgTFIrWRKtH3M+G5TaR28eNdnHRkS zmDcXfLv6Dhv9lEAcfIkFfzzNcCCzJi8YA9xBc+8YuQeEEXosgX/S91vOOpd3OKWk6L6v EzUTnz4lMCfTU+tE+xGg/5sCY551IMdGqZSAKi9zAiS8hyUXdYvxHrziiOGMw7+h0nuNW ZuI63TolMzBvwsRl1qQpYOtqKo5TO46zPPAmioB3RPwoPT4JN0k3tF5eLtLC7FcPaXw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154294; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=I6By4EgpHYT6koviCdzjuU6bqJZD7zzjyiIoL2o4lk8=; b=S6/H7NgJBPrqEPN0296Aj67+6KDEjm+XAWNiT0anS8KVqrachFRM5g2TVADogUI/NNJm syN8X0fqvjvRRSlF2E2MzJ/J2FU6CJMbzhbrTQrdvxaYJHe0ajsG/HI3PH1b208vx/4FW eBD9bMh0sJWj/a4jyG5u+easUBVehOm26GSNzSC8Jgx51sUg2FDU10OHFv+gofLpdM7cl dC2u7k5axWgUgODwhLIscHi/JHddLDjgrr/AjJbYUdHr81R4NBf+NyMQL6MT/pqJQKDp/ iMIXs9Hh1V0VKhGy+nnX8NQXpqlnyQiSRHMUzDXe07UiU3TfpRM4375LdS97j1bdylQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=mROpIiAc; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 596A760A2621 for ; Fri, 20 Nov 2026 05:58:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=mROpIiAc Received: by smtp.kernel.org (Postfix) with ESMTPSA id AA4951F000EE; Fri, 20 Nov 2026 05:58:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154294; bh=I6By4EgpHYT6koviCdzjuU6bqJZD7zzjyiIoL2o4lk8=; h=From:To:Cc:Subject:Date:Reply-To; b=mROpIiAcvr6s6JjgJsS2BbAE/ybUZupv5AA4ISyOL7hXYGDzO8fzqMvArQgIx7Iuv 4ndlVfAJ28gbQVHj7gcquNu3XUptofYyfagff2SvvFHkHHAYPipDPyI5QENtj4RoUW 1OgFg3zoz/AmnW7e0cOhX9QgU9ZKhwvrCkRcrrCU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99693: ocfs2/dlm: serialize migration MLE cleanup on failure Date: Fri, 20 Nov 2026 06:51:19 +0100 Message-ID: <2026112059-CVE-2026-99693-bb5d@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=6800; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ZVjV+rVBGpxsXyYej+VU2Axt5UcUpseVM0/gKfKj1BM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/77ffWf8ju0xY22WVg/fiBZ/rW1gE7eIvNG9K7pDIe f//vJ1NRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzEyJZhnlbLb8m2B4f1WNqi zdN8lr2b/W3JBIb50cZf5i1NUr3Aw71dPNuJS9A3+5UaAA== 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: ocfs2/dlm: serialize migration MLE cleanup on failure A migration MLE has a base reference for the mastering answer and an in-use reference held by dlm_migrate_lockres(). The finishing assertion consumes the base reference, but migration failure drops it again without checking whether the assertion already consumed it. The target queues its migration worker before it acknowledges the ALL_DONE packet, so its finishing assertion can be handled while the sender still waits for the status. If the connection fails before the status arrives, dlm_send_one_lockres() returns an error for a migration that the target has already completed: Old-master sender Finishing assertion ----------------- ------------------- publish MLE; take in-use reference send ALL_DONE; wait for status take lookup reference unlink MLE put lookup and base references send returns a connection error put base reference again; free MLE put in-use reference; access freed MLE dlm_assert_master_handler() holds dlm->spinlock from the MLE lookup to the final puts, and it takes dlm->master_lock around the unlink and the puts. Decide under the same locks: if the MLE is already unhashed, the assertion consumed the base reference, so drop only the sender's in-use reference. Otherwise unlink it before consuming the base reference so a later assertion no longer finds it. An assertion that got there first has also made the target the owner and cleared DLM_LOCK_RES_MIGRATING. Treating the attempt as failed at that point would leave the lockres owned by the target while this node still holds the other nodes' locks and refmap bits, so it could neither be purged nor migrated again. Finish our side as a completed migration does instead: drop those locks under res->spinlock if the target still owns the lockres, and recalculate its usage. Use the same cleanup for the pre-send failure, the send failure and the target-death failure paths. The sender's in-use reference keeps the MLE alive until its final put outside the nested locks. Successful migration retains its existing in-use-only put. A target that has died cannot assert after the sender has seen its death. The o2net node-down callback runs before the DLM one; it disconnects the node and flushes the workqueue that runs the message handlers, so an assertion already received has been handled by the time the DLM removes the node from the domain map. A node that leaves the domain cleanly sends its exit message only after its assertions have been answered. Two windows of the hand-over itself are left as they are: the handler switches the owner and the sender drops the other nodes' locks moments later, and an assertion from a live target that arrives after the sender has given up still meets the owner check in the handler. Waiting for the target before giving up would only stretch the first window into the time in which recovery of the target can observe it. KASAN report, only the relevant frames are kept: BUG: KASAN: slab-use-after-free in dlm_put_mle_inuse+0xce/0xe0 Read of size 8 at addr ffff8881190e3c20 by task umount/593 Call Trace: dlm_put_mle_inuse+0xce/0xe0 dlm_migrate_lockres+0x16af/0x20d0 dlm_empty_lockres+0x60a/0xbd0 dlm_unregister_domain+0x53b/0x11d0 o2cb_cluster_disconnect+0xa5/0x110 ocfs2_cluster_disconnect+0x73/0xc0 ocfs2_dlm_shutdown+0x311/0x440 ocfs2_dismount_volume+0x696/0x940 generic_shutdown_super+0x15f/0x490 kill_block_super+0x40/0xa0 deactivate_locked_super+0xae/0x120 deactivate_super+0xa2/0xc0 cleanup_mnt+0x217/0x450 task_work_run+0x144/0x230 Allocated by task 593: kmem_cache_alloc_noprof+0x20b/0x5c0 dlm_migrate_lockres+0x20e/0x20d0 dlm_empty_lockres+0x60a/0xbd0 dlm_unregister_domain+0x53b/0x11d0 o2cb_cluster_disconnect+0xa5/0x110 ocfs2_cluster_disconnect+0x73/0xc0 ocfs2_dlm_shutdown+0x311/0x440 ocfs2_dismount_volume+0x696/0x940 Freed by task 593: kmem_cache_free+0x242/0x580 __dlm_put_mle+0x4b2/0x660 dlm_migrate_lockres+0x1690/0x20d0 dlm_empty_lockres+0x60a/0xbd0 dlm_unregister_domain+0x53b/0x11d0 o2cb_cluster_disconnect+0xa5/0x110 ocfs2_cluster_disconnect+0x73/0xc0 ocfs2_dlm_shutdown+0x311/0x440 The buggy address belongs to the object at ffff8881190e3c00 which belongs to the cache o2dlm_mle of size 480 The buggy address is located 32 bytes inside of freed 480-byte region [ffff8881190e3c00, ffff8881190e3de0) The Linux kernel CVE team has assigned CVE-2026-99693 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.16 with commit 6714d8e86bf443f6f7af50f9d432025649f091f5 and fixed in 6.12.118 with commit e328dd5207cc67bb283208b47b3a349b9ccd7a20 Issue introduced in 2.6.16 with commit 6714d8e86bf443f6f7af50f9d432025649f091f5 and fixed in 6.18.64 with commit 901b58081cc78ac3cca19eb0e2970cc5f187f367 Issue introduced in 2.6.16 with commit 6714d8e86bf443f6f7af50f9d432025649f091f5 and fixed in 7.3.5 with commit 1696bbf1d6165421a4f7e15549645d96505b0977 Issue introduced in 2.6.16 with commit 6714d8e86bf443f6f7af50f9d432025649f091f5 and fixed in 7.4-rc2 with commit 61469249aab03799b0d3294b7a0cd25dd303017a 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-99693 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/ocfs2/dlm/dlmmaster.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/e328dd5207cc67bb283208b47b3a349b9ccd7a20 https://git.kernel.org/stable/c/901b58081cc78ac3cca19eb0e2970cc5f187f367 https://git.kernel.org/stable/c/1696bbf1d6165421a4f7e15549645d96505b0977 https://git.kernel.org/stable/c/61469249aab03799b0d3294b7a0cd25dd303017a