From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D9A993921EC for ; Sun, 18 Oct 2026 15:53:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792338834; cv=none; b=AXmjQEKHLAmYTRMRPEQ40yvr+odmws+Cm4sFlG9sJUO5VowRFTgGKzg7xik9dgfOiXuydpVgL3eOGQ6ALdjgJGKSp0dtK5+dzoTvkK/Oad9HRnGFwTkm5ZMOF5LkkK2spIB3+l5c+UcMwCJ6d5tp+zz0rlPsiwe/vRFJZ/DMY3A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792338834; c=relaxed/simple; bh=WWxOEFQ724mW/QfgWa5nnSnEs1l6IP1Yfhby6nQD1k8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Neyz3m4OvuADrKfOWtkmDfxfzZvyHBOB/AuU5hB7wJEkuN6HjuM6k3DyeA0wRyfUhkDJn3QMv+knbHjSRYYOKCUj1O9I3QTE1USanRU5hQjvHtw4UCq3WgC3m3jvggEw/pt9UySndLMqbRqgwCiaQs1sP1wGORmdgznyecHO1yw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=v/7LBm93; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="v/7LBm93" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D37101F000C4; Sun, 18 Oct 2026 15:53:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792338833; bh=fGGakg5mAmlIi8m0DN8lwQ2YeZeWDOeAljgroWcQg38=; h=From:To:Cc:Subject:Date:Reply-To; b=v/7LBm93+KoyFon7H+jD7KZpvgY6Mq4yMqLUG0eizzjkNmb/vlh5H9DPw2Nf03Ipb eQ2y/CAtuDSjzSEy1zRThbHvPCPL4qBsczVABRfZc6A0I13It0AB6pcmoyNsI648T1 EGN0Ot1PeFenq1kumKjhbDs8DXDCW/6GSqaJWtug= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98716: KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted Date: Sun, 18 Oct 2026 17:44:51 +0200 Message-ID: <2026101808-CVE-2026-98716-a773@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2883; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=gvb18zty52k4YJYsegigvFsHa9zv0uVdakIR+2lfghU=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlXXnps1Hi/7O2b22XRWjerZU6cn7Jz3hm7k44HY9dNP TN/t+yyhR2xLAyCTAyyYoosX7bxHN1fcUjRy9D2NMwcViaQIQxcnAIwETUThgXzlz/uPKe8UDOs tESkRjTQxd575SyG+S621cZFKctb9xxYPn/pieenK38rcAIA 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: KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12. Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information. The Linux kernel CVE team has assigned CVE-2026-98716 to this issue. Affected and fixed versions =========================== Issue introduced in 4.16 with commit b2ac58f90540e39324e7a29a7ad471407ae0bf48 and fixed in 6.12.113 with commit 74836ae4785b9754bb36d0b18fcc1dec4e5e98d2 Issue introduced in 4.16 with commit b2ac58f90540e39324e7a29a7ad471407ae0bf48 and fixed in 6.18.56 with commit 318ef696fa3c712e46bb62a1a828c3cd62f390c3 Issue introduced in 4.16 with commit b2ac58f90540e39324e7a29a7ad471407ae0bf48 and fixed in 7.2.10 with commit 55865b3ae03705aa39198783b9cb1f8b96eb44e4 Issue introduced in 4.16 with commit b2ac58f90540e39324e7a29a7ad471407ae0bf48 and fixed in 7.3-rc6 with commit 9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85 Issue introduced in 3.16.57 with commit f54d0bb8487d2f016fbc4f0e38ef9098f8eb8bd4 Issue introduced in 4.4.168 with commit 89be8950bab799ddb9cc3777345e3c21bcb32dba 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-98716 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: arch/x86/kvm/svm/svm.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/74836ae4785b9754bb36d0b18fcc1dec4e5e98d2 https://git.kernel.org/stable/c/318ef696fa3c712e46bb62a1a828c3cd62f390c3 https://git.kernel.org/stable/c/55865b3ae03705aa39198783b9cb1f8b96eb44e4 https://git.kernel.org/stable/c/9e06bbb9ade7cdf28d4a3b5b14e5812881c8df85