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 B0D52585970 for ; Fri, 11 Sep 2026 19:58:53 +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=1789156742; cv=none; b=UPI6bO4wSEqu8VBPKYqrv3GVyd4sd+lty70mem3PkI4LPEyGzd9+r7Yg1lncupCOm20ECr4hWV7iYfT3TutaQzWWZrJNqvKwcUKvX5erq0NNJYGetgb94LfRRA5JTUfSDK7GG0jYbWowyY8bHyMtREMYi2y4BBfz6ilS6dG4LYs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156742; c=relaxed/simple; bh=v4u9RT6wwBRrBtPHPRHpQ4LaPtcqQxsTkFh6txI59hM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=rbciu+1PNHTE3UM6upuLEZ7MfgCD44axNV6p9rHYZh4aPo3isAOqmSHS+yf8vsJVu66eIaVLLtFrwUkV4EfbwZrMTpaRMYR2440cVOIgjGIyf1KW0vI1XTMi2jpVL0m9ahg6tXRWuPXpg7cBO8YpuNoIMdh50m0Ob/aFEucJul4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ElcZ+6VX; 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="ElcZ+6VX" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 46ED01F00899; Fri, 11 Sep 2026 19:58:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156732; bh=diPf3SvjiefoojgJDLmVjTAh+IycyQkOuTj/wjeSe6I=; h=From:To:Cc:Subject:Date:Reply-To; b=ElcZ+6VXbU1WyK5BvHa49KQgT49dLHTBLKtyHbyobMt7DKuRJwcIqnOAPmPv+72L1 kshd1i7B0rSR3KXXrIE06B7SMrRa159rTZSAyiB/QZKOfjoNOdFS+FAlfaQ/KQ/eUo 53UPIuT8ETKpBXbfNKMeHL5l9N/4Joi2Lu2M7VUA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89615: fs/ntfs3: bound page_lcns[] index by the log record Date: Fri, 11 Sep 2026 21:45:04 +0200 Message-ID: <2026091136-CVE-2026-89615-82c6@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=3059; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ig6VTlqOlq7yx2RUj5k0WEwwd4W9URwE1cdSxO+EeGA=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIguyVlSsWa/+PGatwcSg/03/nv3xXSsludO+Z+pti cf9T1af7YhlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJ9L9gWLB9e1rBZMVD7xSm GO2reNGSt339mtkMC+a/Tkz93qRXfKhv+cMYu66ShuI/kwA= 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: bound page_lcns[] index by the log record The copy_lcns loop and the redo shorten loop index page_lcns[] at j + i, where i runs up to the log record's lcns_follow. That count is checked only against the record's own length, not the target entry, so check_dp_table() (which validates the entry's lcns_follow) does not cover it: the copy_lcns entry may even be freshly allocated after that check, and find_dp() bounds j but not i. A crafted record thus overflows page_lcns[] of an otherwise valid entry. Add dp_range_ok() and reject, before each loop, any record whose run does not fit the entry. These are the only two page_lcns[] accesses indexed by the record rather than the entry, so together with the entry validation every access is now bounded. [almaz.alexandrovich@paragon-software.com: original patch contained changes to the problem already handled, applied partly] The Linux kernel CVE team has assigned CVE-2026-89615 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit b46acd6a6a627d876898e1c84d3f84902264b445 and fixed in 6.12.109 with commit f4c1bc6d7331f344ffcea93c2a37badcbe15baa6 Issue introduced in 5.15 with commit b46acd6a6a627d876898e1c84d3f84902264b445 and fixed in 6.18.50 with commit 7ccb94901f38a062034b56b43c774050b113758f Issue introduced in 5.15 with commit b46acd6a6a627d876898e1c84d3f84902264b445 and fixed in 7.2.4 with commit 1135ebc225996b3ac1a295652b19a0a706737a6c Issue introduced in 5.15 with commit b46acd6a6a627d876898e1c84d3f84902264b445 and fixed in 7.3-rc1 with commit 6f7b9dbdc1b7520206abce0049bdd143eb536e75 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-89615 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/f4c1bc6d7331f344ffcea93c2a37badcbe15baa6 https://git.kernel.org/stable/c/7ccb94901f38a062034b56b43c774050b113758f https://git.kernel.org/stable/c/1135ebc225996b3ac1a295652b19a0a706737a6c https://git.kernel.org/stable/c/6f7b9dbdc1b7520206abce0049bdd143eb536e75