From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99683: vduse: fix VA/PA confusion in the coherent page fault path
Date: Fri, 20 Nov 2026 06:51:09 +0100 [thread overview]
Message-ID: <2026112055-CVE-2026-99683-17bf@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
vduse: fix VA/PA confusion in the coherent page fault path
vduse_domain_get_coherent_page() assumes that iotlb entries above
bounce_size were installed by vduse_domain_alloc_coherent(), so it
treats map->addr as a physical address. But vduse registers with
use_va = true, and when the device is bound to vhost_vdpa,
vhost_vdpa_va_map() stores a userspace virtual address in map->addr,
which vduse_domain_set_map() then copies into the same iotlb. A
process holding the domain file descriptor across a rebind can
therefore fault in an arbitrary physical page with read/write
access, ignoring the entry permissions.
Additionally, since the domain file mmap lacks VM_IO, the domain
file itself can be mapped and passed to vhost_vdpa_va_map(),
producing self-referential entries that bypass the coherent path
check.
To fix, only translate entries whose backing file is the domain
file itself in vduse_domain_get_coherent_page(), reject such
entries in vduse_domain_set_map() since only external mappings
should be imported, and set VM_IO on the domain file mmap so
vhost_vdpa_va_map() refuses to map it in the first place.
The Linux kernel CVE team has assigned CVE-2026-99683 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 8c773d53fb7b64267b0f55c1d3517cb8c5e29b3c and fixed in 6.12.118 with commit e74a3ed4f59d84036500c5da3905ee40d2c8efa1
Issue introduced in 5.15 with commit 8c773d53fb7b64267b0f55c1d3517cb8c5e29b3c and fixed in 6.18.64 with commit 1b46b4182d3d5c1a085cfe2578048e1ce09e0e01
Issue introduced in 5.15 with commit 8c773d53fb7b64267b0f55c1d3517cb8c5e29b3c and fixed in 7.3.5 with commit 4c8fdb725614189b6c73cf5f7f509592758b6d18
Issue introduced in 5.15 with commit 8c773d53fb7b64267b0f55c1d3517cb8c5e29b3c and fixed in 7.4-rc2 with commit bb2e6f166547838fd7c320b01c90918b736f76e2
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-99683
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/vdpa/vdpa_user/iova_domain.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/e74a3ed4f59d84036500c5da3905ee40d2c8efa1
https://git.kernel.org/stable/c/1b46b4182d3d5c1a085cfe2578048e1ce09e0e01
https://git.kernel.org/stable/c/4c8fdb725614189b6c73cf5f7f509592758b6d18
https://git.kernel.org/stable/c/bb2e6f166547838fd7c320b01c90918b736f76e2
reply other threads:[~2026-11-20 5:57 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=2026112055-CVE-2026-99683-17bf@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.