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 2F37B5867D2 for ; Fri, 11 Sep 2026 19:56:47 +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=1789156616; cv=none; b=rsqIV6YEmPU/SVkKXsV9B4mPY0en6j6weeKlIxBm1pM8BBW4vuNd4bVJSeihltmaXHiCUtYozr71sjiVcYvzECQvKuO46TPtj3XcVDqZm/YXZgRwhAN/7E2VFlRzq4fT4NQJd4uyAIMg+abMNhLVKop/2B+GGIkJ3uwBQV9rpeU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156616; c=relaxed/simple; bh=JCBW2be5KsDvYhBog7k0rFsN+VPb3a7cZmD4g/JoO2s=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=N/02tDG4qXF2HogxJb38SxAyNXFx5zMfX/d13niKBVVE0TTV0lQcGZmzSOmcD3qP3rfA0LiEqG6YPtO2sqHPQd0Wfaoul/ZIWe6jIL9/xjGyV6CEg2F/8YFY3fUVyVwQC3Ge6WXQNzZvh7O30bGBuGQNLCMUuZLEamKgReNbwb8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=oqQLDyO3; 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="oqQLDyO3" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8374D1F000FF; Fri, 11 Sep 2026 19:56:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156607; bh=ncLHi0rfmEpQ4fLimQPjD/PLUlMOGypSRDCn7Yc49SQ=; h=From:To:Cc:Subject:Date:Reply-To; b=oqQLDyO3VZWAPFozTcB9Jrk3Yo7Z8gaAUOs2sjqiDZrL6hVsgW1YYFN6GGhiR1tEd IwIYYWMalidSOZHsjQ48n2/A4iltxCpVWkJNZ7DveQ17EcD+EoeJQpboLo8Y5KFJzQ gu1gy/bVUZolTn4TUtimGiTXlypbF3l3Kv5o5h4U= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89573: dm array: reject an array block whose value size is not the caller's Date: Fri, 11 Sep 2026 21:44:22 +0200 Message-ID: <2026091126-CVE-2026-89573-a132@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=2956; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=8/CV97qWMOy6w8yib8PFDrzr4NpaMNurMhm43hVLxMk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLItMsHilcs+l9//Fr4pJ/GtcW6BV+8ZywPSqsIDBqn 4mckdK3jlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIuhzDgg3vFlrrX52yOeqB lP8qs4cHYjO85jPMT3HfHR3R6bbfRbHnURdTtfTGLxYpAA== 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: reject an array block whose value size is not the caller's array_block_check() can only compare the header against itself, so a block with value_size 4 and max_entries 1018 is internally consistent and passes. dm-cache keeps two arrays -- mappings at 8 bytes and hints at 4 -- and the roots for both live in the superblock. Point the mappings root at a hint block and __load_mappings() walks it through an info whose value size is 8, so element_at() strides 8 bytes over 4-byte entries and reaches offset 8160 of a 4096-byte block. get_ablock() and __shadow_ablock() are the two places that hold the block and the caller at once. Reject there when the two value sizes disagree. Arrays only ever read their own blocks, so this fires on crafted metadata only. The Linux kernel CVE team has assigned CVE-2026-89573 to this issue. Affected and fixed versions =========================== Issue introduced in 3.9 with commit 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 and fixed in 6.12.109 with commit 7bf4b5cb42a4e27f36bcbc6209d82a5da9c0168c Issue introduced in 3.9 with commit 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 and fixed in 6.18.50 with commit ac4a5eb8b002a0742c938fc98b922e243f53573a Issue introduced in 3.9 with commit 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 and fixed in 7.2.4 with commit cb409b38b0232ee4385ef55cddcd6fbdd011a8a2 Issue introduced in 3.9 with commit 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 and fixed in 7.3-rc1 with commit 4538a287bdf5d0f9a379c678e5262b9f5783f547 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-89573 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/7bf4b5cb42a4e27f36bcbc6209d82a5da9c0168c https://git.kernel.org/stable/c/ac4a5eb8b002a0742c938fc98b922e243f53573a https://git.kernel.org/stable/c/cb409b38b0232ee4385ef55cddcd6fbdd011a8a2 https://git.kernel.org/stable/c/4538a287bdf5d0f9a379c678e5262b9f5783f547