{"metadata": {"vulnerability": "CVE-2026-99346", "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-99346", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:22:01.304Z", "date_only": false, "value": "2026-11-19T14:22:01.304Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99346", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:53:18.791Z", "date_only": false, "value": "2026-11-19T14:53:18.791599Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117643673487489023", "record": "CVE-2026-99346", "field": "creation_timestamp", "uuid": "342fa4f7-9123-4734-8504-4a4ecc5c9ea1", "content": "CVE-2026-99346 KVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch In the Linux kernel, the following vulnerability has been resolved:\nKVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch\nWhen the pCPU where the VMCB was most recently used is switched, resetthe ASID generation in both VMCBs, triggering new ASID allocation forthe immediate VMRUN as well as the next VMRUN on the other VMCB.\nThe ASID is shared between vmcb01 and vmcb02, and gets flushed on everynested transition. However, since pCPU tracking is done per VMCB, it ispossible for one VMCB to allocate a new ASID when migrated to a newpCPU, and then the other VMCB reuses that ASID on the old pCPU. This canresult in the same ASID being used by multiple vCPUs on the old pCPU.\nExample scenario:- vCPU runs on pCPU A, vmcb01 is active, asid=1.- vCPU migrates to pCPU B, vmcb01 pCPU changes, new asid=2.- Another vCPU runs on pCPU A and allocates asid=2 as well.- vCPU migrates back to pCPU A, and then switches to vmcb02 before it  runs again with vmcb01.- No pCPU switch is detected for vmcb02, so VMRUN is done with asid=2.- Two vCPUs end up using asid=2 on the same pCPU.\nKeep the VMCB dirtying to the active VMCB only. Clean bits are trackedby a pCPU for each VMCB, so do not unnecessarily dirty a VMCB if itspCPU does not change.\nAdditionally, initialize the tracked pCPU for vmcb02 to -1 on nestedenablement as hardening, so that a new ASID allocation is alwaystriggered when nested is disabled and re-enabled.\nNo performance regression was noticed when overcommitting L1 vCPUs in L0(to force rescheduling), pinning L1 &lt;-&gt; L2 vCPUs, and running CPUID in atight loop bouncing between 2 vCPUs in L2.\nAn alternative (and perhaps more proper) fix would be tracking the ASIDper-VMCB instead (e.g. [1]). However, that's a more involved change, andit would result in having different ASIDs for L1 and L2 without actuallyproperly maintaining them. It would probably work because all TLBflushes target the current VMCB, and the other VMCB is always flushed onnested transitions, but the code ends up in an arguably more fragilestate. Punt a proper clean fix to an incoming (and overdue) overhaul ofSVM's ASID usage [2].\n[1] https://lore.kernel.org/lkml/20250205182402.2147495-2-yosry.ahmed@linux.dev[2] https://lore.kernel.org/kvm/20260728003557.1136583-1-yosry@kernel.org\nhttps://www.cve.org/CVERecord?id=CVE-2026-99346https://git.kernel.org/stable/c/5636d57b61068918085360aaad18ab57872e5800https://git.kernel.org/stable/c/058173bce103b6ac405b2bbf61e29a7f3767348fhttps://git.kernel.org/stable/c/7d787fb34e825218702496fb0d5892529bea9366https://git.kernel.org/stable/c/bf260dc9e7b8bfcd06c1a8e739797b1cf0917c72#kernel #Linux#CVE_2026_99346#bot", "url": "https://infosec.exchange/users/cve/statuses/117643673487489023"}, {"timestamp": "2026-11-19T15:17:45Z", "date_only": false, "value": "2026-11-19T15:17:45Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-VMH6-434H-9MPM", "record": "GHSA-VMH6-434H-9MPM", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:17:45.830Z", "date_only": false, "value": "2026-11-19T15:17:45.830", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99346", "record": "FKIE_CVE-2026-99346", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:17:45.830Z", "date_only": false, "value": "2026-11-19T15:17:45.830", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99346", "record": "FKIE_CVE-2026-99346", "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-VMH6-434H-9MPM", "record": "GHSA-VMH6-434H-9MPM", "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-VMH6-434H-9MPM", "record": "GHSA-VMH6-434H-9MPM", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-20T05:11:38.533Z", "date_only": false, "value": "2026-11-20T05:11:38.533Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99346", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-20T05:11:38.533Z", "date_only": false, "value": "2026-11-20T05:11:38.533Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99346", "field": "containers.cna.providerMetadata.dateUpdated"}, {"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-99346", "record": "DEBIAN-CVE-2026-99346", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T06:18:13.894Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:22:01.304Z", "date_only": false, "value": "2026-11-19T14:22:01.304Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99346", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:22:01.304Z", "date_only": false, "value": "2026-11-19T14:22:01.304Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99346", "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": 57372.590083, "hours": 15.936830578611112, "days": 0.6640346074421296, "min_seconds": 57372.590083, "max_seconds": 57372.590083, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:22:01.304Z", "date_only": false, "value": "2026-11-19T14:22:01.304Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99346", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T06:18:13.894Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
