From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
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 [thread overview]
Message-ID: <2026091126-CVE-2026-89573-a132@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2026-09-11 19:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091126-CVE-2026-89573-a132@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.