{"metadata": {"vulnerability": "CVE-2026-99338", "count": 11, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 6}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.409Z", "date_only": false, "value": "2026-09-25T10:25:14.409Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99338", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:21:46.037Z", "date_only": false, "value": "2026-11-19T14:21:46.037Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99338", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:34:56.101Z", "date_only": false, "value": "2026-11-19T14:34:56.101Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99338", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:34:56.101Z", "date_only": false, "value": "2026-11-19T14:34:56.101Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99338", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:47:55.716Z", "date_only": false, "value": "2026-11-19T14:47:55.716845Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117643652314559417", "record": "CVE-2026-99338", "field": "creation_timestamp", "uuid": "b8c74b0e-5db9-49fc-b592-b6446ad99451", "content": "CVE-2026-99338 KVM: TDX: Enable Notify VM exit In the Linux kernel, the following vulnerability has been resolved:\nKVM: TDX: Enable Notify VM exit\nEnable Notify VM exit functionality for TDX guests.\nNotify VM exit is an existing feature supported by KVM.  Userspace canenable Notify VM exit through KVM_CAP_X86_NOTIFY_VMEXIT when it'sreported as supported.  However, KVM reports the support of this CAP justbased on the hardware capability but doesn't differentiate between VMXand TDX.  This leads to the issue that userspace can enable this cap forTDX guests without getting an error, but the feature is not actuallyenabled because KVM doesn't call the TDX module API to program therelevant TD VMCS fields.\nEnable Notify VM exit for TDX guests by:\n  - 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.\n  - Adding corresponding exit handler for TDX Notify VM Exit.\nNotify VM exit can happen when executing the IRET instruction.  If theIRET unblocks the NMI blocking state, bit 12 of the exit qualificationis set.  In this case, the VMM needs to restore the \"blocked by NMI\" statewhen it decides to re-enter the guest.  For TDX, KVM cannot manage theGUEST_INTERRUPTIBILITY_INFO and it's TDX module's responsibility tohandle it.  Extract the common part without NMI blocking handling into ahelper in common.h so that it can be shared between VMX and TDX.\nNote, KVM uses \"pre-production\" terminology for the feature formally calledNotify VM-Exit.  All public versions of the SDM refer to the feature asInstruction Timeout.  This will be remedied in the near future, for now,use KVM's terminology for consistency.\nNote, #2, there is no enumeration bit for Notify VM exit by TDX modulebecause all TDX modules support it, and allow to set the correspondingTD VMCS fields as long as the hardware supports the feature.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99338https://git.kernel.org/stable/c/216729d9780df7d4cf91435af38c8f65d51ce93dhttps://git.kernel.org/stable/c/02b92b0d7cdcda3c1f7196a3210bbe867ae6693ehttps://git.kernel.org/stable/c/d93395058c1951bb657c8895dd1fc0f22263f1cc#kernel #Linux#CVE_2026_99338#bot", "url": "https://infosec.exchange/users/cve/statuses/117643652314559417"}, {"timestamp": "2026-11-19T15:17:44Z", "date_only": false, "value": "2026-11-19T15:17:44Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-PC86-G3CQ-2WV4", "record": "GHSA-PC86-G3CQ-2WV4", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:17:44.850Z", "date_only": false, "value": "2026-11-19T15:17:44.850", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99338", "record": "FKIE_CVE-2026-99338", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:17:44.850Z", "date_only": false, "value": "2026-11-19T15:17:44.850", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99338", "record": "FKIE_CVE-2026-99338", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-19T15:31:21Z", "date_only": false, "value": "2026-11-19T15:31:21Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-PC86-G3CQ-2WV4", "record": "GHSA-PC86-G3CQ-2WV4", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:31:21Z", "date_only": false, "value": "2026-11-19T15:31:21Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-PC86-G3CQ-2WV4", "record": "GHSA-PC86-G3CQ-2WV4", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-20T05:12:10.083Z", "date_only": false, "value": "2026-11-20T05:12:10.083058+00:00", "kind": "other", "label": "Updated", "source": "debian_tracker \u00b7 DEBIAN-CVE-2026-99338", "record": "DEBIAN-CVE-2026-99338", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T06:17:51.595Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:21:46.037Z", "date_only": false, "value": "2026-11-19T14:21:46.037Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99338", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:21:46.037Z", "date_only": false, "value": "2026-11-19T14:21:46.037Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99338", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 57365.558161, "hours": 15.934877266944445, "days": 0.6639532194560185, "min_seconds": 57365.558161, "max_seconds": 57365.558161, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:21:46.037Z", "date_only": false, "value": "2026-11-19T14:21:46.037Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99338", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T06:17:51.595Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
