[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122415-CVE-2025-68743-f0bb@gregkh>
Date: Wed, 24 Dec 2025 13:10:19 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68743: mshv: Fix create memory region overlap check
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mshv: Fix create memory region overlap check
The current check is incorrect; it only checks if the beginning or end
of a region is within an existing region. This doesn't account for
userspace specifying a region that begins before and ends after an
existing region.
Change the logic to a range intersection check against gfns and uaddrs
for each region.
Remove mshv_partition_region_by_uaddr() as it is no longer used.
The Linux kernel CVE team has assigned CVE-2025-68743 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 621191d709b14882270dfd8ea5d7d6cdfebe2c35 and fixed in 6.17.13 with commit 2183924dd834e0703f87e17c17e689bcbf55d69d
Issue introduced in 6.15 with commit 621191d709b14882270dfd8ea5d7d6cdfebe2c35 and fixed in 6.18.2 with commit ab3e7a78d83a61d335458cfe2e4d17eba69ae73d
Issue introduced in 6.15 with commit 621191d709b14882270dfd8ea5d7d6cdfebe2c35 and fixed in 6.19-rc1 with commit ba9eb9b86d232854e983203dc2fb1ba18e316681
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-2025-68743
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/hv/mshv_root_main.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/2183924dd834e0703f87e17c17e689bcbf55d69d
https://git.kernel.org/stable/c/ab3e7a78d83a61d335458cfe2e4d17eba69ae73d
https://git.kernel.org/stable/c/ba9eb9b86d232854e983203dc2fb1ba18e316681
Powered by blists - more mailing lists