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 641D158E2BD for ; Fri, 11 Sep 2026 19:59: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=1789156754; cv=none; b=e/Y2xBBtIVWoOV0FA3MVk9xhrbQkrAT2yLhJcSY+/ermKYmyT+/0n6YWQfnPADsxRz1elNdd5paVC4ZAXKQVbv9Av5wSPob+mXSD5jVXS1K5qdQoubDWnG5gOq1Oqv31n9dPqCfX+4GzMjMtjZffQE+rtWRKIXLkfrpN0o3B7AI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156754; c=relaxed/simple; bh=cjzIY/MA70rbapO/Hm6j4eg+Iy3ZqXR5pwE3ECx1rdE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=UWPMOaFowHeLqQBeprFQ5M48sWyAWXLloEB6Hb3hULUe3/leNBPYRAbp+h2PDI8mnZd7tSg401/AhsTJdEB2PbkHMtdT4vcQSq/ziJT6bZsM4t5WdUI0TIP81f5c3hfUia0PR8Ra72USW46ZNokan6t1rkMBdi0VC9pwLnRWVTo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=fp+5HT7Z; 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="fp+5HT7Z" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 18A881F000FF; Fri, 11 Sep 2026 19:59:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156741; bh=rVg9Ijjpajlsefrh/f5hwQoJMDQSUxhj/eYlWRyGjRg=; h=From:To:Cc:Subject:Date:Reply-To; b=fp+5HT7ZmHBW9V1ppnwZFB4KGhRkjCEszQ7mWJWndE8ZQe9bD2rlsCRFF7w2H2UTm t3CX/zA+vJ+qWy3N0x0kyD3OJk0N8jIO8Lsxxnlxf01wPaIrr6cVUjF9Fn7DRiZPPs AstXss+ppUOCb063xO1vQh3ZWsMNt+aCnCc43gBc= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89617: fs/ntfs3: validate dirty page table on log replay Date: Fri, 11 Sep 2026 21:45:06 +0200 Message-ID: <2026091136-CVE-2026-89617-4aba@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=3075; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=cA+dRcxd+R31hrYWjaKmZzeyfeawi/d2T3p9xt9JUJo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIgsyLx0Oa7GbOiNjQUXBs6ttZ/otFDnO35+0Qv2/2 IUbpuENHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRrj6GeTachk9zSu4svq++ 6X/fT5XSbRsj3jMs2L678Vn10rxT6r4JpVe05Lwz1nO9BgA= 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: fs/ntfs3: validate dirty page table on log replay Each DIR_PAGE_ENTRY ends in a page_lcns[] array whose length is the on-disk lcns_follow field. check_rstbl() validates the table bookkeeping but never checks that this array fits in the entry, so a crafted lcns_follow lets the v0->v1 conversion memmove and later replay passes run off the entry. Add check_dp_table() to reject, right after check_rstbl(), any entry larger than its size claims via struct_size() (the same expression used to allocate these entries, so the check is overflow-safe by construction). All consumers can then trust lcns_follow as the real capacity. This covers every page_lcns[] access whose index is bounded by the entry itself (the conversion memmove, the HotFix store via find_dp(), and the self-bounded scan loops). Accesses whose index comes from the log record need a separate bound and are handled in a follow-up patch. The Linux kernel CVE team has assigned CVE-2026-89617 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit b46acd6a6a627d876898e1c84d3f84902264b445 and fixed in 6.12.109 with commit 1200c2779c43b62656ccbb67df9468a7a9af2484 Issue introduced in 5.15 with commit b46acd6a6a627d876898e1c84d3f84902264b445 and fixed in 6.18.50 with commit 2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56 Issue introduced in 5.15 with commit b46acd6a6a627d876898e1c84d3f84902264b445 and fixed in 7.2.4 with commit 0908da07c23be4f94b99dfd9a94765525f0fe4bd Issue introduced in 5.15 with commit b46acd6a6a627d876898e1c84d3f84902264b445 and fixed in 7.3-rc1 with commit 006cb7713dec10368e699abc4367e5faa334c9a5 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-89617 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/ntfs3/fslog.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/1200c2779c43b62656ccbb67df9468a7a9af2484 https://git.kernel.org/stable/c/2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56 https://git.kernel.org/stable/c/0908da07c23be4f94b99dfd9a94765525f0fe4bd https://git.kernel.org/stable/c/006cb7713dec10368e699abc4367e5faa334c9a5