From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46327: dm: fix unlocked test for dm_suspended_md
Date: Tue, 9 Jun 2026 14:25:10 +0200 [thread overview]
Message-ID: <2026060909-CVE-2026-46327-aaef@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
dm: fix unlocked test for dm_suspended_md
The function dm_blk_report_zones tests if the device is suspended with
the "dm_suspended_md" call. However, this function is called without
holding any locks, so the device may be suspended just after it.
Move the call to dm_suspended_md after dm_get_live_table, so that the
device can't be suspended after the suspended state was tested.
The Linux kernel CVE team has assigned CVE-2026-46327 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12.34 with commit f9c1bdf24615303d48a2d0fd629c88f3189563aa and fixed in 6.12.75 with commit 175ac0a6115400278d3900f5a04a58b17b3f6cd0
Issue introduced in 6.16 with commit 37f53a2c60d03743e0eacf7a0c01c279776fef4e and fixed in 6.18.14 with commit 7a3385e97af2b6f485fef11e82d8c29adee4be93
Issue introduced in 6.16 with commit 37f53a2c60d03743e0eacf7a0c01c279776fef4e and fixed in 6.19.4 with commit d809a36692ee1394cac85ce6ba7cf8ea58da5812
Issue introduced in 6.16 with commit 37f53a2c60d03743e0eacf7a0c01c279776fef4e and fixed in 7.0 with commit 24c405fdbe215c45e57bba672cc42859038491ee
Issue introduced in 6.15.3 with commit d19bc1b4dd5f322980b1f05f79b2ea4f0db10920
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-46327
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-zone.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/175ac0a6115400278d3900f5a04a58b17b3f6cd0
https://git.kernel.org/stable/c/7a3385e97af2b6f485fef11e82d8c29adee4be93
https://git.kernel.org/stable/c/d809a36692ee1394cac85ce6ba7cf8ea58da5812
https://git.kernel.org/stable/c/24c405fdbe215c45e57bba672cc42859038491ee
reply other threads:[~2026-06-09 12:26 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=2026060909-CVE-2026-46327-aaef@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox