From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154263; b=fjAo//vhpXNJ76rycmLit6Wf/h/b5j6mPl5V9mTWfcABWOdADLH8vXYFw1ro5HhJ33lK xnlrVmx2Qw7CQgdlZopg6NkS0QRDmrWQCoLfS/STyt+w9+Jm9gJG435zcc7JMHhOXFrCb ui45ZbNRVeJiw3aY1OQh/0LpGSsNceP8eXX9xwLfEfKbWgtObqGklj5Hg0nXoVH9qk2CG +6vliOJOIpXZPzbDz1AuO5xh52yvQjwgVmImFhjyMXUcWqZ95oFar3r0h71ft0vSAozUL dZ964LfSyf9+Ygmv59qqBepObG0BHfzYMrD5GdcMA0+VISVT2PDw6onkvSeMLGE1ReQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154263; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=4iUiyMMkX+nfUSr5/juGW0/h5TcixHHw+6ohb5X6lBI=; b=GJv3SOYzq3J5Ly4EhiYssbgMTAMxYZZTu/CMR64sKsg1YIHs34hd2KPAZAGRnoT+s5g8 cDukFBjiE7NXMqazA7xlzYVUdGss0FWWzdF1y8l0iLtytsuWwzcxqQtV1ht4Gb3oefgmG DjT5daz9rX96tEe6R/GLlzB3L0oxKGzzMfiqaiL02LC6uT6LObpXIAIpNG5fVcXhF7LFO txbYujWID3vvRnCOSSXb0AvwR5Bxlw0l+P7xqSlq0ItklqAYXRL9WilwIVdi/LvU0hYDn 2M8TloBgcsJ4AzdUAgfJ+601Wy9Rh1i4bJPWdAIBwHGT0mz6XJsuO6x12SdRKdIBgTg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=SUugD950; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EE727606A338 for ; Fri, 20 Nov 2026 05:57:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=SUugD950 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 14F671F000D1; Fri, 20 Nov 2026 05:57:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154262; bh=4iUiyMMkX+nfUSr5/juGW0/h5TcixHHw+6ohb5X6lBI=; h=From:To:Cc:Subject:Date:Reply-To; b=SUugD950uNiYRLe2aBl74tIFV+rtrVCVOfepmr2ic0ECQaslVKkMsKfw9+IJzmTvx yoAVGM0HPNStVpiVdMra0+QAcIkjNsO+/wmRmXKvlrfMXQWQjYNF6f5DGO+NEoS4ns Rv6if6i6/pOEBMnO0o3V+QuvhrPDtYHOh5y8PEP0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99683: vduse: fix VA/PA confusion in the coherent page fault path Date: Fri, 20 Nov 2026 06:51:09 +0100 Message-ID: <2026112055-CVE-2026-99683-17bf@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3319; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ny1u6AUV3tiTS68IbqJxqMd0UZbwqsLCamcOCC29vtw=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7zdf3sjHtqPtfK67+AoLd9NHUQy7WH8U1b6/quJ3r eYN19mUjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjIkcsMC2ZN1c4QuKLxrKkr T2aFQU7KbbOaGQwLGjZoOlQkHnu4OvBi4vLFs6fOOOi3EgA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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