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=1795154297; b=h6dgD82pLwm4mK8ZpujnKc55eyIdaqnq6cA0XKxNEvQn1SuLl0R+gyy/SUnJ+8A/lO0R 22Cx4QfyXz5X4N9lP0wjt8EJou81N5y5Arf0xplGvhycXQZSX2F/aXxkjy06oQrm1h8EP ma73OoaR5fMCctx+HsRKVYk4ypzb0XYxk+DmYbBNZnnWU/Xjd3rEx80xG5tkwRG07plBU UND7YnMfe74fDHAtMuGSmJIXpo7A/XFTnAaDKnn8ejIq8uZ7hLB0ZhGtQzsZ+l4lb2OTm FLltAZoxbbHbZkuYWDwmEdasNg7qxwaZIDETPS7cgpS31npnscr0cvFPQ+ui36Gl0Mw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154297; 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=fFT0+PdHzKdqmMhftC6HitlHWkCRpsVawnPhsYKd2eg=; b=r+0R3pUOgsWpof+sHCs6w7YSn38OpJ7hsqYoNaoAbWFQb23YsYtrHwm088h8TLIOXvPT PK/DCUIUTa/PSKdSvHv+331YC2cNz7kuqz7wOv2maqBeFzEkIIfvl48tmf0NlANqRkoeW AmJ4VlxGZDikuxG0+zicw3hGfkZxxZPkzelTBnJauAtvb9EUiw9lzbLatgPP5goArPPQz yO7XCGX05ab+scIxEynvUeQH0pJkn5RzEzqg3qeejxaXEei/G7Lu5fdx19Ut/zjGCl7Ru bY5XOakb6PbpgjwBD9Z8SPsJ9nKQXMZOCZh8mmgckESGm5i00iwN4wP8tf3SccxhkAQ== 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=wGRJ5TYW; 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 3CE0060A6F43 for ; Fri, 20 Nov 2026 05:58:17 +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=wGRJ5TYW Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8CAE01F000EF; Fri, 20 Nov 2026 05:58:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154297; bh=fFT0+PdHzKdqmMhftC6HitlHWkCRpsVawnPhsYKd2eg=; h=From:To:Cc:Subject:Date:Reply-To; b=wGRJ5TYWZD/nVqq0JxbxYLWT0Uy/rjO+897dLqwrf85qkAY5KiszH19Z1Kb73OoqH wBxGURVXzb6gshvUKv89CD3LEcM6bhvlLI488lXnDAInPv6yGXs2lTCKyfi8PdsBdp EDP1yA+Wzr2CCn6DFAYiiai5COz6IF26SXao/BQs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99694: ocfs2: do not index before the entry array when dividing an empty bucket Date: Fri, 20 Nov 2026 06:51:20 +0100 Message-ID: <2026112059-CVE-2026-99694-0c69@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=3918; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=feNtD0XpB4hsACnj3U9xWIk9tARoScG5WzNmdb9o+X0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/77c/38ve5xW0f9tDjn+Lnv2wfdq1h8tn9fsf8gVnJ nDJe0061BHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATcStjmF+sfFFnvcevzmNR 8Wviy6P2vm1sT2JY0Dp5yt/bgtL67y4y8Ev3rfOWM3dVAwA= 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: do not index before the entry array when dividing an empty bucket ocfs2_divide_xattr_bucket() appends an empty bucket carrying a sentinel hash when the source bucket has no divide position, taking that hash from xh_entries[start - 1]. ocfs2_xattr_find_divide_pos() returns count when every entry shares one hash, and its loop does not run at all for count < 2, so an empty bucket comes back with start == count == 0 and the read is xh_entries[-1]. That is outside the __counted_by_le(xh_count) bounds of xh_entries[] and lands on the header, so the value picked up is xh_count | xh_free_start << 16. One above it is written into the new bucket's xh_entries[0] and committed, which leaves a bucket whose first hash does not follow the bucket before it. ocfs2_xattr_bucket_find() binary searches on xh_entries[0], so the broken key hides the range the sentinel was meant to cover: getxattr() answers -ENODATA for an attribute that is stored, and an insert can go to the wrong bucket and leave two copies of a name. The cross cluster divide hands the same value back as a tree record's e_cpos, which then claims a hash range it does not cover. Read xh_entries[0] instead. The branch is only reached when every entry shares one hash, so for a non-empty bucket it holds the same value, and for an empty one it is the slot that carries the bucket key. An empty bucket reaches the divide from ocfs2_check_xattr_bucket_collision(), which reports no collision for one, through ocfs2_add_new_xattr_bucket() and ocfs2_extend_xattr_bucket(). It does not take a failed set to get there: a divide that finds no position is itself what leaves an empty sentinel bucket behind, and a later extend can pick it as the target. The Linux kernel CVE team has assigned CVE-2026-99694 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.28 with commit 80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913 and fixed in 6.12.118 with commit 58308e76c036822c78947efbbdcb800c1df6f6b2 Issue introduced in 2.6.28 with commit 80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913 and fixed in 6.18.64 with commit 7148fa383fb000d3125989ff3e63f3458a33591d Issue introduced in 2.6.28 with commit 80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913 and fixed in 7.3.5 with commit b710975d07b049c957ba6b93985b1cf9b169ad6e Issue introduced in 2.6.28 with commit 80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913 and fixed in 7.4-rc2 with commit 7133a0d0954c109f1764ebf8ab32d7e757a6c587 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-99694 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/xattr.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/58308e76c036822c78947efbbdcb800c1df6f6b2 https://git.kernel.org/stable/c/7148fa383fb000d3125989ff3e63f3458a33591d https://git.kernel.org/stable/c/b710975d07b049c957ba6b93985b1cf9b169ad6e https://git.kernel.org/stable/c/7133a0d0954c109f1764ebf8ab32d7e757a6c587