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 F22434F96B6 for ; Thu, 17 Sep 2026 16:21:13 +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=1789662075; cv=none; b=e3Bj2JCDUfRjxg7ViFLaybMzAEfNdKTz/Vuiat615m86AMvy2cQAxMqPm7mpvgbCs9DuzIWrY/cSJTVvb9PA4qCDRbhMnQ1U+TSSwttsoCgwvPiajHqihAA4RrN2gnXBjnewdM3jr3+1LHF92NUW3C1ddKWueAUV/qfwsBYCXcs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789662075; c=relaxed/simple; bh=aM9dzcOlGM0t+oVb282Ytd6rIDvkoXC+gVo1V/EPBc4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=HeNF2X7GrnlOAaWJNp0UjOVcVnEO1eqC6EvBRFOtPT7+fhZ5dhh3heMQHYAVyD3cLl46D++JsBZ2FVk/2UZpfzEalEE7eAQ7GLhyeUIVu8M7UcedkCnvUSCtTwdMCDvuSA+fW/FFkb3Yuu/XWQzFiUNINBXFEARV1nDhlZJwJKI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=QSuTWLwx; 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="QSuTWLwx" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 560E31F000FF; Thu, 17 Sep 2026 16:21:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789662073; bh=SddmmzPl0GWJOVPoB+DhNkTZdKWL7Dt5y52sUm0vBRw=; h=From:To:Cc:Subject:Date:Reply-To; b=QSuTWLwxqFjlAcq6puUxc+uJau2GrRgHFOkvUJ+6pa/DdASaRPCpFRORGeWKjA8o7 WjdiOYwQ9wmFQ9/cynaLx9nzAcFzC39PGZu0XOHEnj5feh8+QpmE6ahhfJ11XxbAPJ XK4Ah1y6j2ONAGOkWzgdoBHPqX7x0BL48u8AJcUA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-90205: ocfs2: validate orphan slot during inode read Date: Thu, 17 Sep 2026 17:10:35 +0100 Message-ID: <2026091735-CVE-2026-90205-e6bc@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=3835; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=MSpa+r21m6NZJ0/MpCHLUhrUYOa4N3eskDt5Qb6xfyQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBJqz/vDELRD66WNm+l23yOVL6WOzWx4Hl/ky7WNr2 /x+Xe37jlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjIu5UMC9pNJ2xgz83RMJ26 0+CvgLPuJlfffQxzuG47xrhP3+U/gVX54uRpO2t2X/ylDAA= 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: validate orphan slot during inode read Patch series "ocfs2: validate active orphan slots during inode read". OCFS2 trusts active ordinary and append-DIO orphan slots read from dinodes. A corrupted slot can therefore index osb_orphan_wipes or the slot-local system-inode cache outside their allocations before the corruption is reported. Patch 1 validates the ordinary orphan slot used by inode wipe processing. Patch 2 validates the append-DIO orphan slot used by DIO completion and orphan recovery. Both checks reject corrupt metadata at the existing inode validation boundary. This patch (of 2): [BUG] A corrupted dinode with OCFS2_ORPHANED_FL can carry an i_orphaned_slot outside the mounted filesystem slot range. ocfs2_wipe_inode() uses it to index osb_orphan_wipes before looking up the orphan directory, causing an out-of-bounds memory access. BUG: KASAN: slab-use-after-free in ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102 Read of size 8 at addr ffff88800b767c00 by task kworker/u8:3/85 Call Trace: ... ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102 ocfs2_wipe_inode+0x292/0xf70 fs/ocfs2/inode.c:840 ocfs2_delete_inode fs/ocfs2/inode.c:1155 [inline] ocfs2_evict_inode+0x6c9/0x1170 fs/ocfs2/inode.c:1295 evict+0x38e/0x8f0 fs/inode.c:810 iput_final fs/inode.c:1914 [inline] iput fs/inode.c:1966 [inline] iput+0x55b/0x8b0 fs/inode.c:1926 ocfs2_recover_orphans+0x610/0xe40 fs/ocfs2/journal.c:2374 ocfs2_complete_recovery+0x5af/0xd00 fs/ocfs2/journal.c:1373 ... [CAUSE] ocfs2_validate_inode_block() validates i_suballoc_slot but leaves the active ordinary orphan slot unchecked. Downstream consumers assume that the value is smaller than osb->max_slots. [FIX] Reject an active i_orphaned_slot outside the slot range during dinode validation, before the inode reaches orphan wipe processing. The Linux kernel CVE team has assigned CVE-2026-90205 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.16 with commit b4df6ed8db0c387d38292e31f00adc4cd297ed5a and fixed in 6.18.52 with commit c6c908f9b4edfb04534b15573168ae038f7a9cbf Issue introduced in 2.6.16 with commit b4df6ed8db0c387d38292e31f00adc4cd297ed5a and fixed in 7.2.6 with commit 3d7c4b7ce7b4baedfd8699fa692cd95f77d332de Issue introduced in 2.6.16 with commit b4df6ed8db0c387d38292e31f00adc4cd297ed5a and fixed in 7.3-rc1 with commit b2d31acbd3b182755b019183fb46949ba5e39b9f 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-90205 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/inode.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/c6c908f9b4edfb04534b15573168ae038f7a9cbf https://git.kernel.org/stable/c/3d7c4b7ce7b4baedfd8699fa692cd95f77d332de https://git.kernel.org/stable/c/b2d31acbd3b182755b019183fb46949ba5e39b9f