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=1795099077; b=KLkLq14pkUuIoSJP9J3sMroJ5Dwawrb2sU4YAoxQKgNs3hSpvwsOQ5cqILhV/7oCQD4t nu+cdGzWXfWNYkOGlANeMCY7zUK2fTrPBWhtl/tdDGEF6PoDI5LzwPm/JnzH7BpQu9Q+L 6wS+hkTpYwzQrchteTX3JxyCgaAP0ViH0PqIE+qQUHMa3pPRvmjKD5rtf/DZHyWkyUmd9 JZeD59lwvIdDFcCiJJey483quT1mMB4G6rUYcF94z83AxEykbOAljJXztMpvD8jKHKVDE bSYAyYwqUkgK82JB4GRzYDxUwQc+x7bqh7rcj9V9x3nRP30ZC8LQ/fxiP9fiCglXe0w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795099077; 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=NMf2vm0ZyVZwiepgbv2i1WmeU5kR62bIRmSDef5GynI=; b=wCwdFABJLs//qfKw29lWKBtHtlT37++qNusBF9eV/iV7a1kYbcyQJIt2hNPCEXFGSbUs 6rA+k9FZug6Zi8UnPJsOuD7VcEhA8aGq5rMl7fptJRX8H1fCJU3wbBXq6lT9Af9XwbPMf tzC0w1AaDkQmINLJm7b2RDUlPMsMf+2oUJ1zAf0XuJ8MzzZPEkXYcl0ckx7Dph96ijh+T ybsaxMpP8uaYgdX0RpQvNRDHqj1jX2hpFaDNrmCzHkRkVK8tkBOPrnnXf22p8m2nIH6+d x2x1dS1GZ5rovAv1R7WVna6zJ99b7Kl+fEobtDPtq4nCz3pkV5EMBTonxX8M+l+JGyg== 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=sjIKyoKt; 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 6A875606A326 for ; Thu, 19 Nov 2026 14:37:57 +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=sjIKyoKt Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4C3421F000C5; Thu, 19 Nov 2026 14:37:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795099077; bh=NMf2vm0ZyVZwiepgbv2i1WmeU5kR62bIRmSDef5GynI=; h=From:To:Cc:Subject:Date:Reply-To; b=sjIKyoKtGoPuRQWykGzWlLoI+UUSoVEZkeB07AiSX5QlXu7zxfatse4rS7ZwixmWn cnX5LZY4pF7weXj8dVu+cCEWTMGGqo+4xWJdExE5DNEq9vBbEzmFBBItkQnKVG+/5X rjmHGzQp5LBtX+s0Xg2sDv5k4b0sLzP/sZDVSds8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99338: KVM: TDX: Enable Notify VM exit Date: Thu, 19 Nov 2026 15:23:56 +0100 Message-ID: <2026111945-CVE-2026-99338-e3f2@gregkh> X-Mailer: git-send-email 2.56.0 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=3956; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=2UrRSFsNuW2Uw3FnR0j3RAMsNj7D9ByQXcimhnyZSxQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2QrZPvEu/jRzZeqchfPnLO28FnklU50x+rfJ7+T56 w99vqVp3xHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQAT+XSJYUH7tWd6dxS7Ok12 6K78nvR+bd/l3SkMC7Y3fbtQ2fTUpnvhlbS+f0f7oy1ymgA= 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: TDX: Enable Notify VM exit Enable Notify VM exit functionality for TDX guests. Notify VM exit is an existing feature supported by KVM. Userspace can enable Notify VM exit through KVM_CAP_X86_NOTIFY_VMEXIT when it's reported as supported. However, KVM reports the support of this CAP just based on the hardware capability but doesn't differentiate between VMX and TDX. This leads to the issue that userspace can enable this cap for TDX guests without getting an error, but the feature is not actually enabled because KVM doesn't call the TDX module API to program the relevant TD VMCS fields. Enable Notify VM exit for TDX guests by: - Invoking TDX module API calls to set NOTIFY_VM_EXITING and Notify Window in TD VMCS. It's done in tdx_vcpu_init() where other TD VMCS bits are set. Since TDX vCPU cannot be reset, it only needs to be configured once when initializing the TDX vCPU. - Adding corresponding exit handler for TDX Notify VM Exit. Notify VM exit can happen when executing the IRET instruction. If the IRET unblocks the NMI blocking state, bit 12 of the exit qualification is set. In this case, the VMM needs to restore the "blocked by NMI" state when it decides to re-enter the guest. For TDX, KVM cannot manage the GUEST_INTERRUPTIBILITY_INFO and it's TDX module's responsibility to handle it. Extract the common part without NMI blocking handling into a helper in common.h so that it can be shared between VMX and TDX. Note, KVM uses "pre-production" terminology for the feature formally called Notify VM-Exit. All public versions of the SDM refer to the feature as Instruction Timeout. This will be remedied in the near future, for now, use KVM's terminology for consistency. Note, #2, there is no enumeration bit for Notify VM exit by TDX module because all TDX modules support it, and allow to set the corresponding TD VMCS fields as long as the hardware supports the feature. The Linux kernel CVE team has assigned CVE-2026-99338 to this issue. Affected and fixed versions =========================== Issue introduced in 6.16 with commit 161d34609f9b319d0706eaf7d2cb7a2731251b25 and fixed in 6.18.61 with commit 216729d9780df7d4cf91435af38c8f65d51ce93d Issue introduced in 6.16 with commit 161d34609f9b319d0706eaf7d2cb7a2731251b25 and fixed in 7.3.2 with commit 02b92b0d7cdcda3c1f7196a3210bbe867ae6693e Issue introduced in 6.16 with commit 161d34609f9b319d0706eaf7d2cb7a2731251b25 and fixed in 7.4-rc1 with commit d93395058c1951bb657c8895dd1fc0f22263f1cc 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-99338 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/vmx/common.h arch/x86/kvm/vmx/tdx.c arch/x86/kvm/vmx/vmx.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/216729d9780df7d4cf91435af38c8f65d51ce93d https://git.kernel.org/stable/c/02b92b0d7cdcda3c1f7196a3210bbe867ae6693e https://git.kernel.org/stable/c/d93395058c1951bb657c8895dd1fc0f22263f1cc