From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89575: dm raid1: reserve space for NUL-terminator in build_constructor_string()
Date: Fri, 11 Sep 2026 21:44:24 +0200 [thread overview]
Message-ID: <2026091127-CVE-2026-89575-c71c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
dm raid1: reserve space for NUL-terminator in build_constructor_string()
Reserve space for the termination NUL after the maximum 20 decimal
digits of a long long value to avoid buffer overflow in sprintf().
The Linux kernel CVE team has assigned CVE-2026-89575 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.31 with commit f5db4af466e2dca0fe822019812d586ca910b00c and fixed in 6.12.109 with commit 0a3657ebd6b517b60cdc5123894047616974e25b
Issue introduced in 2.6.31 with commit f5db4af466e2dca0fe822019812d586ca910b00c and fixed in 6.18.50 with commit 644140527ae494cedf3b5c0ecd16287deaea7a66
Issue introduced in 2.6.31 with commit f5db4af466e2dca0fe822019812d586ca910b00c and fixed in 7.2.4 with commit f79b53ca3a68a46c6fc3b30b148d1dfb1b33ea8b
Issue introduced in 2.6.31 with commit f5db4af466e2dca0fe822019812d586ca910b00c and fixed in 7.3-rc1 with commit 73c37fe54cd056d07461b142ab0b8b81e1ef6ad8
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-89575
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/dm-log-userspace-base.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/0a3657ebd6b517b60cdc5123894047616974e25b
https://git.kernel.org/stable/c/644140527ae494cedf3b5c0ecd16287deaea7a66
https://git.kernel.org/stable/c/f79b53ca3a68a46c6fc3b30b148d1dfb1b33ea8b
https://git.kernel.org/stable/c/73c37fe54cd056d07461b142ab0b8b81e1ef6ad8
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=2026091127-CVE-2026-89575-c71c@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.