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 E2CF3584949 for ; Fri, 11 Sep 2026 19:56:50 +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=1789156629; cv=none; b=bqdY2N3DUwGp3aEvOXVxajhWCCCpJoPQp3/K1NT9eP/t+z15U64HzWCLyA9daNwa5l+QmC+43Z8Ymyo3s4cnQsT9mY78QC1Oj1TGMEz+axZfofz/uef/w6FypvKvi9eShkVyotRaJx3gbd/wt1Tafs6eBg3mWGYpqJ5KCF/bZkE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156629; c=relaxed/simple; bh=/ZkZ09APOs9+9IaXloMQwpJyCK2Lu5sM/ykgemN9Jjk=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=o7s2FavLw4PY530cHeu+2eWHJJioq42mdizPZgxnmOG1gSghkBcbQUnYS7YHd1futF8HKRxBxidVmxFVAKw2WX0ifyLG7i3V3ywkDNkJE6cb4yt+qwFOrIK5jI7OReUXKZfbKDwPD65HLo715HfSCCVJaAaaQK/nE3ZGkfH315s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ZBSqPe62; 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="ZBSqPe62" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 83C0B1F0089A; Fri, 11 Sep 2026 19:56:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156610; bh=H5Z9+Cy86vQSEP9HZImi+sK8vQ+zOcxhL8+YSeFOpGE=; h=From:To:Cc:Subject:Date:Reply-To; b=ZBSqPe62R+UWdo1kEVWRb5srVKg8byFGGG7Jkr9NLLOAxJYjVTxiBS9IusDPwANQ0 r4hu9zq5ij3KbqtG2lRAgUIeBqAYUBJ9nDXFTrfs0m68sw0ksW1zj3GRkGO8QX9Rfi PUt1CmmMFHYXUePS6UzydO1V7+OtALuwvWD1Ij2A= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89574: dm array: validate array block headers on read Date: Fri, 11 Sep 2026 21:44:23 +0200 Message-ID: <2026091126-CVE-2026-89574-087e@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=3076; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=k+Q+2l6j0UJUkJGSOjLDTCvLgYPMojEKKHYAtGSCt4g=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLItOeemmySFZ0t9esyuXj13co/H2yLn/lau6XvD+Dy 6vPNtZ0xLIwCDIxyIopsnzZxnN0f8UhRS9D29Mwc1iZQIYwcHEKwERs8xnmu574nxqprm//b5PZ 98w54TPfpi/rYFhwrlj/hTLrzx2h8Y0nmARlrxzsKVgLAA== 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: dm array: validate array block headers on read array_block_check() validates blocknr and csum and nothing else, while node_check(), next to it, has bounded the structural fields since both were written. dm_array_cursor_next() takes its loop bound from the on-disk nr_entries and element_at() is unguarded pointer arithmetic, so a count larger than the block holds keeps the cursor in one block while the index grows past it and the read walks off the dm-bufio buffer -- dm_cache_load_mappings() drives it once per cache block at activation. Check the header against itself: reject a zero value_size, require max_entries to equal calc_max_entries() for that value_size and block size, and require nr_entries to fit. Equality rather than an upper bound, since a count below the real capacity trips BUG_ON() in fill_ablock() and trim_ablock(). Metadata dm-array writes satisfies all three. The Linux kernel CVE team has assigned CVE-2026-89574 to this issue. Affected and fixed versions =========================== Issue introduced in 3.9 with commit 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 and fixed in 6.12.109 with commit 67adda7ed5da3e3b64f5b9021a02c21fb374fd9c Issue introduced in 3.9 with commit 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 and fixed in 6.18.50 with commit b33f76d33aaeacf3baf3370d8d64985169b36600 Issue introduced in 3.9 with commit 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 and fixed in 7.2.4 with commit 9808ddffb4bc659352df3020cd84d9d864820ee5 Issue introduced in 3.9 with commit 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 and fixed in 7.3-rc1 with commit 2965787723084835b18dfe993cd450ebf5bd4540 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-89574 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: drivers/md/persistent-data/dm-array.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/67adda7ed5da3e3b64f5b9021a02c21fb374fd9c https://git.kernel.org/stable/c/b33f76d33aaeacf3baf3370d8d64985169b36600 https://git.kernel.org/stable/c/9808ddffb4bc659352df3020cd84d9d864820ee5 https://git.kernel.org/stable/c/2965787723084835b18dfe993cd450ebf5bd4540