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=1795100038; b=gX4RsVhAlNeiCwQ2sCCQ1S8VTr7mXljmX7vAN/dARepl5rjOzsvXMyunQQXLrOupBbun H1J2Mu1liKRvPZBVPk3OhNayEtPntj72izR37JkUzFbkLYh/P1ooi7wvhRG8OrWtw24We oUJ/W3ayibchXbW8qr+a3GZWkUrpatqWOKoaqTCvrlyEYQ8Hq3up3TICBI4gmRePQEqtJ xwm0ObFhdTspEWNT0rIj3aKULt45+SAgugmEXaSYCYMHYbl5k/dVortujURQkRn37/w8u B6U/ABiwA946gkXgfw0XoVzVJ9DSfBfDdWYGl1qvLOJsMOxT+9W+chEeLN/8LsLxCqQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795100038; 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=7fLUbHznM9MyQ6jLWApFaXaQZaRgVIfLUMUR4QeWdOI=; b=XLqsx72b/DdmdcRdnSWrm1yu5CnJKcPIl9JtirSr3hrvACbrKQlb98k9Go44gPVRddgQ FxJ9X4Ez54CBOXzP/8WkfAPMBcEh+vBOvNVD5cR+K/FTPJvYvgzcBy7ziZSTZKGpaviyJ r7QevXiw8mxXHdR19qrHRHrj9iU/6dACeotwuERsFu7TGi2/IQ2C8n6AaVQmlmXiFrMjm UUkzjlo+T7xXpKbACsuUtmWOqM5LZsl7rg2fEJ3gmd3oTWaRM8/R4Gv+FXxERVv+/p+Xi LoWpm06whCXzJ7RFIF6ENOrztSJDaOGIS5CS5EVaqhxoCnqoY8xg3RFVc6LrviAEhcg== 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=T6qW+h9o; 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 416AC606A320 for ; Thu, 19 Nov 2026 14:53:58 +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=T6qW+h9o Received: by smtp.kernel.org (Postfix) with ESMTPSA id 44F021F000C4; Thu, 19 Nov 2026 14:53:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795100038; bh=7fLUbHznM9MyQ6jLWApFaXaQZaRgVIfLUMUR4QeWdOI=; h=From:To:Cc:Subject:Date:Reply-To; b=T6qW+h9orwkId0vBv5kMPR69M6iYTJJ6xgw8yO1tzgtcfkliW7dyp0pW+stS6KNHM mKKXrtSuYXPp0c3wis+0+HBFR71L0HmufR+w3HsQdDqZE6OVBpKUzqovJN8FGMGQK6 i525NOdRFActyRysDJ0ro6ooAvHDU5eOgz11+zps= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99428: ocfs2: snapshot dentry names in file and setattr traces Date: Thu, 19 Nov 2026 15:25:26 +0100 Message-ID: <2026111902-CVE-2026-99428-5ebe@gregkh> X-Mailer: git-send-email 2.56.0 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=7137; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Q/gY7DWOcFi7Tk7dAv0myO56myk0KbFJFD+bX85wWF8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2Zr0uLfe/aQg7fc+9sCsxxmL9vbLKDu0F6T9vLNxv /Ln0olLO2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAiBfIM82MmT2Z67e/A8Xrz Id8doQGn5rce0GGYn/t19Zun6ZfOnrggsEXGVH2+2vxWJQA= 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: snapshot dentry names in file and setattr traces Patch series "ocfs2: stabilize dentry names in file and setattr traces", v4. Snapshot names at all six users of ocfs2__file_ops and at the separate setattr event. Patch 1 handles the five ordinary file-operation callers and setattr. Patch 2 handles release separately to preserve its locked open-count sample and take the snapshot outside that critical section. The release explanation distinguishes its existing RCU lifetime coverage from name/length consistency. It does not claim that the ordinary callers' external-name UAF interleaving crosses the held inode spinlock. The release source change is unchanged from v3. Patch 1 also removes the read callback's redundant NULL-inode check. The two patches apply independently and leave trace formats unchanged. This patch (of 2): The open, fsync, read, write and splice-read trace calls pass the live dentry name and length to the shared ocfs2__file_ops event class. ocfs2_setattr() passes the same unprotected arguments to its own event. Both events size and copy a __string field separately. A reference to the dentry does not pin the external storage backing an individual name. With an event enabled, a caller can be preempted after loading the name pointer. A long-to-short rename can then replace the name and reclaim its old external allocation before the trace callback sizes or copies it, provided no other snapshot retains that allocation. The setattr inode lock does not exclude every rename: a same-directory rename of a source directory need not take that directory's inode lock. It can therefore change the dentry name while setattr records its event. Inline names and separately loaded lengths can also change during trace record sizing and copying. Take a dentry name snapshot around each of these six trace calls and pass both the string and length from the snapshot. Check event enablement before taking a snapshot. Keep the event classes and formats unchanged. Also remove the redundant NULL-inode check in the read callback. file_inode() returns the open file's inode, which is already used by the trace call above the check. The historical report below is from the read path. KASAN report as below: BUG: KASAN: slab-use-after-free in strlen+0x85/0xa0 Read of size 1 at addr ffff88810a5b2b18 by task python3/496 [CPU and host details omitted.] Call Trace: dump_stack_lvl+0x93/0xd0 print_report+0xce/0x630 ? strlen+0x85/0xa0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x20e/0x420 ? strlen+0x85/0xa0 kasan_report+0xe0/0x110 ? strlen+0x85/0xa0 strlen+0x85/0xa0 trace_event_raw_event_ocfs2__file_ops+0xf0/0x480 ? __pfx_trace_event_raw_event_ocfs2__file_ops+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? pmbd_probe_hit_cookie+0xe7/0x1c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __pfx_pmbd_probe_hit_cookie+0x10/0x10 ocfs2_file_read_iter+0x6cd/0xb30 ? __pfx_ocfs2_file_read_iter+0x10/0x10 ? selinux_file_permission+0x11d/0x540 ? srso_alias_return_thunk+0x5/0xfbef5 ? security_file_permission+0x26/0x80 vfs_read+0x7d2/0xc20 ? __pfx_vfs_read+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? __pfx_do_sys_openat2+0x10/0x10 ksys_read+0x111/0x200 ? __pfx_ksys_read+0x10/0x10 ? irqentry_exit+0xbe/0x820 ? srso_alias_return_thunk+0x5/0xfbef5 ? trace_hardirqs_on_prepare+0x11d/0x150 ? srso_alias_return_thunk+0x5/0xfbef5 do_syscall_64+0x114/0x620 entry_SYSCALL_64_after_hwframe+0x77/0x7f [User register dump omitted.] Allocated by task 489: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 __kmalloc_noprof+0x2de/0x780 __d_alloc+0x5fc/0x8c0 d_alloc_parallel+0x106/0x11d0 lookup_open+0x3ff/0x13e0 path_openat+0x95e/0x2020 do_file_open+0x21e/0x470 do_sys_openat2+0xf4/0x1b0 __x64_sys_openat+0x136/0x1e0 do_syscall_64+0x114/0x620 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 0: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x5f/0x80 __rcu_free_sheaf_prepare+0x65/0x2a0 rcu_free_sheaf_nobarn+0x1d/0x50 rcu_core+0x6be/0x1ed0 handle_softirqs+0x1fa/0x8d0 __irq_exit_rcu+0x113/0x1e0 irq_exit_rcu+0xe/0x20 sysvec_apic_timer_interrupt+0x6c/0x80 asm_sysvec_apic_timer_interrupt+0x1a/0x20 The buggy address belongs to the object at ffff88810a5b2b00 which belongs to the cache kmalloc-rcl-192 of size 192 The buggy address is located 24 bytes inside of freed 192-byte region [ffff88810a5b2b00, ffff88810a5b2bc0) [Page and shadow-memory dumps omitted.] The Linux kernel CVE team has assigned CVE-2026-99428 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.39 with commit 468eedde23d6c9335935773f4f5764267d5a7763 and fixed in 6.12.117 with commit 84908981fbda3c133b60e75568d853d3191f9fb2 Issue introduced in 2.6.39 with commit 468eedde23d6c9335935773f4f5764267d5a7763 and fixed in 6.18.61 with commit f976692490bbdf670d4cc241b8951c8cfddb1583 Issue introduced in 2.6.39 with commit 468eedde23d6c9335935773f4f5764267d5a7763 and fixed in 7.3.2 with commit d2052367cbdad321d131e6280f41c4be5a1b5c96 Issue introduced in 2.6.39 with commit 468eedde23d6c9335935773f4f5764267d5a7763 and fixed in 7.4-rc1 with commit 8cd3ff30659775a6831c66687a69d2b83d163591 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-99428 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/file.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/84908981fbda3c133b60e75568d853d3191f9fb2 https://git.kernel.org/stable/c/f976692490bbdf670d4cc241b8951c8cfddb1583 https://git.kernel.org/stable/c/d2052367cbdad321d131e6280f41c4be5a1b5c96 https://git.kernel.org/stable/c/8cd3ff30659775a6831c66687a69d2b83d163591