{"metadata": {"vulnerability": "CVE-2026-99336", "count": 11, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 6}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.408Z", "date_only": false, "value": "2026-09-25T10:25:14.408Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99336", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:21:42.304Z", "date_only": false, "value": "2026-11-19T14:21:42.304Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99336", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:34:20.129Z", "date_only": false, "value": "2026-11-19T14:34:20.129Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99336", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:34:20.129Z", "date_only": false, "value": "2026-11-19T14:34:20.129Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99336", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:46:35.001Z", "date_only": false, "value": "2026-11-19T14:46:35.001194Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117643647029162122", "record": "CVE-2026-99336", "field": "creation_timestamp", "uuid": "6cdec5c7-9fc7-45df-acd3-fa451366e687", "content": "CVE-2026-99336 KVM: guest_memfd: take the invalidate lock when unbinding a dying file In the Linux kernel, the following vulnerability has been resolved:\nKVM: guest_memfd: take the invalidate lock when unbinding a dying file\nkvm_gmem_unbind() takes mapping-&gt;invalidate_lock only if theget_file_active() succeeds. When the guest_memfd file is dying, itsreference count is already zero so get_file_active fails and the bindingis removed without holding the invalidate lock.\nkvm_gmem_invalidate_{start,end}() checks f-&gt;bindings independently todecide whether to begin or end KVM MMU invalidation. So, the bindingsmust therefore remain stable between the two calls. Otherwise, unbindcan remove a binding after start increments mmu_invalidate_in_progress,but before end finds the binding and decrements it.Example, unbind race with memory failure:\n  CPU 0: memory failure               CPU 1: memslot delete  ----------------------------------  ---------------------------                                      (guest_memfd file is dying)  kvm_gmem_error_folio()    kvm_gmem_invalidate_start()      finds binding      mmu_invalidate_in_progress++                                      kvm_gmem_unbind()                                        get_file_active() fails                                        removes binding    kvm_gmem_invalidate_end()      no binding found      counter stays elevated\nmmu_invalidate_retry() then returns 1 forever, so guest page faultsretry without ever installing a mapping and the guest hangs.\nRemove the distinction between live and dying files in the unbind path.Always use slot-&gt;gmem.file and take the invalidate lock when it's non-NULL.Normal unbind callers hold slots_lock, which prevents release from clearingthe pointer or freeing the file state until unbind completes. Final VMteardown can only see a NULL pointer because guest_memfd pins the KVM untilrelease has cleared all bindings.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99336https://git.kernel.org/stable/c/4ae4316682cdc78d8f5a856ab0712a8281f211cahttps://git.kernel.org/stable/c/3af94f4e3526efdf52d84d7ba8d9fb8e8facb93ahttps://git.kernel.org/stable/c/024be82ac4c4df650cc6daca6d7db79daee95470https://git.kernel.org/stable/c/0ee2c883b62deb74d8c43007e8049dc006d3a2fb#kernel #Linux#CVE_2026_99336#bot", "url": "https://infosec.exchange/users/cve/statuses/117643647029162122"}, {"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-GH4C-W75C-262G", "record": "GHSA-GH4C-W75C-262G", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:17:44.610Z", "date_only": false, "value": "2026-11-19T15:17:44.610", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99336", "record": "FKIE_CVE-2026-99336", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:17:44.610Z", "date_only": false, "value": "2026-11-19T15:17:44.610", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99336", "record": "FKIE_CVE-2026-99336", "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-GH4C-W75C-262G", "record": "GHSA-GH4C-W75C-262G", "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-GH4C-W75C-262G", "record": "GHSA-GH4C-W75C-262G", "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-99336", "record": "DEBIAN-CVE-2026-99336", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T06:21:12.681Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:21:42.304Z", "date_only": false, "value": "2026-11-19T14:21:42.304Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99336", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:21:42.304Z", "date_only": false, "value": "2026-11-19T14:21:42.304Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99336", "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": 57570.377668, "hours": 15.991771574444444, "days": 0.6663238156018518, "min_seconds": 57570.377668, "max_seconds": 57570.377668, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:21:42.304Z", "date_only": false, "value": "2026-11-19T14:21:42.304Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99336", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T06:21:12.681Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
