CVE-2026-99338 (GCVE-0-2026-99338)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:21 – Updated: 2026-11-19 14:34| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
161d34609f9b319d0706eaf7d2cb7a2731251b25 , < 216729d9780df7d4cf91435af38c8f65d51ce93d
(git)
Affected: 161d34609f9b319d0706eaf7d2cb7a2731251b25 , < 02b92b0d7cdcda3c1f7196a3210bbe867ae6693e (git) Affected: 161d34609f9b319d0706eaf7d2cb7a2731251b25 , < d93395058c1951bb657c8895dd1fc0f22263f1cc (git) |
guessed | |
| Linux | Linux |
Affected:
6.16
Unaffected: 0 , < 6.16 (semver) Unaffected: 6.18.61 , ≤ 6.18.* (semver) Unaffected: 7.3.2 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/vmx/common.h",
"arch/x86/kvm/vmx/tdx.c",
"arch/x86/kvm/vmx/vmx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "216729d9780df7d4cf91435af38c8f65d51ce93d",
"status": "affected",
"version": "161d34609f9b319d0706eaf7d2cb7a2731251b25",
"versionType": "git"
},
{
"lessThan": "02b92b0d7cdcda3c1f7196a3210bbe867ae6693e",
"status": "affected",
"version": "161d34609f9b319d0706eaf7d2cb7a2731251b25",
"versionType": "git"
},
{
"lessThan": "d93395058c1951bb657c8895dd1fc0f22263f1cc",
"status": "affected",
"version": "161d34609f9b319d0706eaf7d2cb7a2731251b25",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/vmx/common.h",
"arch/x86/kvm/vmx/tdx.c",
"arch/x86/kvm/vmx/vmx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.16"
},
{
"lessThan": "6.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"versionStartIncluding": "6.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "6.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "6.16",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: TDX: Enable Notify VM exit\n\nEnable Notify VM exit functionality for TDX guests.\n\nNotify VM exit is an existing feature supported by KVM. Userspace can\nenable Notify VM exit through KVM_CAP_X86_NOTIFY_VMEXIT when it\u0027s\nreported as supported. However, KVM reports the support of this CAP just\nbased on the hardware capability but doesn\u0027t differentiate between VMX\nand TDX. This leads to the issue that userspace can enable this cap for\nTDX guests without getting an error, but the feature is not actually\nenabled because KVM doesn\u0027t call the TDX module API to program the\nrelevant TD VMCS fields.\n\nEnable Notify VM exit for TDX guests by:\n\n - Invoking TDX module API calls to set NOTIFY_VM_EXITING and Notify\n Window in TD VMCS. It\u0027s done in tdx_vcpu_init() where other TD VMCS\n bits are set. Since TDX vCPU cannot be reset, it only needs to be\n configured once when initializing the TDX vCPU.\n\n - Adding corresponding exit handler for TDX Notify VM Exit.\n\nNotify VM exit can happen when executing the IRET instruction. If the\nIRET unblocks the NMI blocking state, bit 12 of the exit qualification\nis set. In this case, the VMM needs to restore the \"blocked by NMI\" state\nwhen it decides to re-enter the guest. For TDX, KVM cannot manage the\nGUEST_INTERRUPTIBILITY_INFO and it\u0027s TDX module\u0027s responsibility to\nhandle it. Extract the common part without NMI blocking handling into a\nhelper in common.h so that it can be shared between VMX and TDX.\n\nNote, KVM uses \"pre-production\" terminology for the feature formally called\nNotify VM-Exit. All public versions of the SDM refer to the feature as\nInstruction Timeout. This will be remedied in the near future, for now,\nuse KVM\u0027s terminology for consistency.\n\nNote, #2, there is no enumeration bit for Notify VM exit by TDX module\nbecause all TDX modules support it, and allow to set the corresponding\nTD VMCS fields as long as the hardware supports the feature."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:34:56.101Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/216729d9780df7d4cf91435af38c8f65d51ce93d"
},
{
"url": "https://git.kernel.org/stable/c/02b92b0d7cdcda3c1f7196a3210bbe867ae6693e"
},
{
"url": "https://git.kernel.org/stable/c/d93395058c1951bb657c8895dd1fc0f22263f1cc"
}
],
"title": "KVM: TDX: Enable Notify VM exit",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99338",
"datePublished": "2026-11-19T14:21:46.037Z",
"dateReserved": "2026-09-25T10:25:14.409Z",
"dateUpdated": "2026-11-19T14:34:56.101Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/vmx/common.h",
"arch/x86/kvm/vmx/tdx.c",
"arch/x86/kvm/vmx/vmx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "216729d9780df7d4cf91435af38c8f65d51ce93d",
"status": "affected",
"version": "161d34609f9b319d0706eaf7d2cb7a2731251b25",
"versionType": "git"
},
{
"lessThan": "02b92b0d7cdcda3c1f7196a3210bbe867ae6693e",
"status": "affected",
"version": "161d34609f9b319d0706eaf7d2cb7a2731251b25",
"versionType": "git"
},
{
"lessThan": "d93395058c1951bb657c8895dd1fc0f22263f1cc",
"status": "affected",
"version": "161d34609f9b319d0706eaf7d2cb7a2731251b25",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/vmx/common.h",
"arch/x86/kvm/vmx/tdx.c",
"arch/x86/kvm/vmx/vmx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.16"
},
{
"lessThan": "6.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: TDX: Enable Notify VM exit\n\nEnable Notify VM exit functionality for TDX guests.\n\nNotify VM exit is an existing feature supported by KVM. Userspace can\nenable Notify VM exit through KVM_CAP_X86_NOTIFY_VMEXIT when it\u0027s\nreported as supported. However, KVM reports the support of this CAP just\nbased on the hardware capability but doesn\u0027t differentiate between VMX\nand TDX. This leads to the issue that userspace can enable this cap for\nTDX guests without getting an error, but the feature is not actually\nenabled because KVM doesn\u0027t call the TDX module API to program the\nrelevant TD VMCS fields.\n\nEnable Notify VM exit for TDX guests by:\n\n - Invoking TDX module API calls to set NOTIFY_VM_EXITING and Notify\n Window in TD VMCS. It\u0027s done in tdx_vcpu_init() where other TD VMCS\n bits are set. Since TDX vCPU cannot be reset, it only needs to be\n configured once when initializing the TDX vCPU.\n\n - Adding corresponding exit handler for TDX Notify VM Exit.\n\nNotify VM exit can happen when executing the IRET instruction. If the\nIRET unblocks the NMI blocking state, bit 12 of the exit qualification\nis set. In this case, the VMM needs to restore the \"blocked by NMI\" state\nwhen it decides to re-enter the guest. For TDX, KVM cannot manage the\nGUEST_INTERRUPTIBILITY_INFO and it\u0027s TDX module\u0027s responsibility to\nhandle it. Extract the common part without NMI blocking handling into a\nhelper in common.h so that it can be shared between VMX and TDX.\n\nNote, KVM uses \"pre-production\" terminology for the feature formally called\nNotify VM-Exit. All public versions of the SDM refer to the feature as\nInstruction Timeout. This will be remedied in the near future, for now,\nuse KVM\u0027s terminology for consistency.\n\nNote, #2, there is no enumeration bit for Notify VM exit by TDX module\nbecause all TDX modules support it, and allow to set the corresponding\nTD VMCS fields as long as the hardware supports the feature."
}
],
"id": "CVE-2026-99338",
"lastModified": "2026-11-19T15:17:44.850",
"metrics": {},
"published": "2026-11-19T15:17:44.850",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/02b92b0d7cdcda3c1f7196a3210bbe867ae6693e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/216729d9780df7d4cf91435af38c8f65d51ce93d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d93395058c1951bb657c8895dd1fc0f22263f1cc"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-19T21:02:23+00:00",
"cve": "CVE-2026-99338",
"id": "CVE-2026-99338",
"initial_release_date": "2026-11-19T14:21:46.037000+00:00",
"product_status:known_affected": "111",
"product_status:known_not_affected": "93",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: kvm: Denial of Service via unconfigured Notify VM-exit for TDX guests",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99338.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.