Skip to main content
VulnerabilityPublished

CVE-2026-99338: Linux kernel · KVM: TDX: Enable Notify VM exit

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99338

Not known to be exploited · fixed in d93395058c1951bb657c8895dd1fc0f22263f1cc : update Linux kernel when convenient.

Data as of 19 Nov 2026, 16:20 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in d93395058c1951bb657c8895dd1fc0f22263f1cc, 216729d9780df7d4cf91435af38c8f65d51ce93d, 02b92b0d7cdcda3c1f7196a3210bbe867ae6693e

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to d93395058c1951bb657c8895dd1fc0f22263f1cc, 216729d9780df7d4cf91435af38c8f65d51ce93d or 02b92b0d7cdcda3c1f7196a3210bbe867ae6693e.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 161d34609f9b319d0706eaf7d2cb7a2731251b25, < d93395058c1951bb657c8895dd1fc0f22263f1cc
Fixed in
  • d93395058c1951bb657c8895dd1fc0f22263f1cc
LinuxLinuxAffected
  • ≥ 161d34609f9b319d0706eaf7d2cb7a2731251b25, < 216729d9780df7d4cf91435af38c8f65d51ce93d
Fixed in
  • 216729d9780df7d4cf91435af38c8f65d51ce93d
LinuxLinuxAffected
  • ≥ 161d34609f9b319d0706eaf7d2cb7a2731251b25, < 02b92b0d7cdcda3c1f7196a3210bbe867ae6693e
Fixed in
  • 02b92b0d7cdcda3c1f7196a3210bbe867ae6693e
LinuxLinuxAffected
  • =6.16
Fixed in–

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.

References

Community reviews

Loading reviews…