{"metadata": {"vulnerability": "CVE-2026-99472", "count": 11, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 6}, "linked_omitted": 0}, "data": [{"timestamp": "2026-09-25T10:25:14.417Z", "date_only": false, "value": "2026-09-25T10:25:14.417Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99472", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-19T14:42:59.997Z", "date_only": false, "value": "2026-11-19T14:42:59.997Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99472", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-19T14:42:59.997Z", "date_only": false, "value": "2026-11-19T14:42:59.997Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99472", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-19T14:42:59.997Z", "date_only": false, "value": "2026-11-19T14:42:59.997Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99472", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-19T15:18:01Z", "date_only": false, "value": "2026-11-19T15:18:01Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-6CJQ-7H3X-F93M", "record": "GHSA-6CJQ-7H3X-F93M", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-19T15:18:01.633Z", "date_only": false, "value": "2026-11-19T15:18:01.633", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99472", "record": "FKIE_CVE-2026-99472", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:18:01.633Z", "date_only": false, "value": "2026-11-19T15:18:01.633", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99472", "record": "FKIE_CVE-2026-99472", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-19T15:31:25Z", "date_only": false, "value": "2026-11-19T15:31:25Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-6CJQ-7H3X-F93M", "record": "GHSA-6CJQ-7H3X-F93M", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-19T15:31:26Z", "date_only": false, "value": "2026-11-19T15:31:26Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-6CJQ-7H3X-F93M", "record": "GHSA-6CJQ-7H3X-F93M", "field": "modified", "linked_record": true}, {"timestamp": "2026-11-19T16:35:40.405Z", "date_only": false, "value": "2026-11-19T16:35:40.405790Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117644075973750133", "record": "CVE-2026-99472", "field": "creation_timestamp", "uuid": "87fbaf04-7226-414e-ad85-affc91b1d4f2", "content": "CVE-2026-99472 KVM: pfncache: use a dedicated invalidation sequence for cache refresh In the Linux kernel, the following vulnerability has been resolved:\nKVM: pfncache: use a dedicated invalidation sequence for cache refresh\nThe gfn_to_pfn_cache refresh path guards against mmu notifierinvalidations which complete while it has dropped gpc-&gt;lock for theHVA-&gt;PFN lookup: hva_to_pfn_retry() samples kvm-&gt;mmu_invalidate_seqand retries if it changed, or if mn_active_invalidate_count is stillelevated.\nThat is insufficient for HVA-based caches. mmu_invalidate_seq is onlyadvanced by kvm_mmu_invalidate_end() when the invalidated rangeoverlaps a memslot, and an HVA-based cache (e.g. the Xen shared_infopage mapped with KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA) need not be backedby any memslot at all. An invalidation of the cached HVA which startsand ends entirely within the lookup window is thus invisible to theretry check: mn_active_invalidate_count is back to zero and thesequence never moved. The refresh then publishes a mapping of a pagewhich has already been freed, and the next reader dereferences it:\n  BUG: KASAN: use-after-free in kvm_xen_shared_info_init+0x3c6/0x440  Read of size 4 at addr ffff8880599c2900 by task syz.2.383/7257\nSince gfn_to_pfn_cache_invalidate_start() deliberately skips cacheswhich are not currently valid (including one whose refresh is inprogress, as the refresh clears the valid flag before dropping thelock), the retry check is the only line of defence, and it must firefor *any* invalidation, not just those hitting a memslot.\nAdd a dedicated kvm-&gt;gpc_invalidate_seq, incremented by everykvm_mmu_notifier_invalidate_range_end() under mn_invalidate_lockbefore mn_active_invalidate_count is decremented, and check it inhva_to_pfn_retry() instead of mmu_invalidate_seq. Incrementing inrange_end() in the same critical section as the in-progress countalso closes the variant where the cache is activated with thecontested HVA only after invalidate_range_start() has run.\nThe same bug is also reachable through the per-vCPU vcpu_info cache(KVM_XEN_VCPU_ATTR_TYPE_VCPU_INFO_HVA), where the stale mapping isthen dereferenced by kvm_setup_guest_pvclock() on the next KVM_RUN:\n  BUG: KASAN: use-after-free in kvm_setup_guest_pvclock+0x5bf/0x660\nThis intentionally makes refresh retry on *unrelated* mmu notifierevents; restoring precision (and reworking the GPC locking moregenerally) is left for a subsequent series.\nReproducers: https://david.woodhou.se/xen_shinfo_race.c             https://david.woodhou.se/vcpu_info_race.c\nhttps://www.cve.org/CVERecord?id=CVE-2026-99472https://git.kernel.org/stable/c/fabc002f6396202b5ad7ad4ceec24d27aad90f3fhttps://git.kernel.org/stable/c/da260bcb56feeb6489a83f310308453a0a7de25e#kernel #Linux#CVE_2026_99472#bot", "url": "https://infosec.exchange/users/cve/statuses/117644075973750133"}, {"timestamp": "2026-11-19T19:09:23.206Z", "date_only": false, "value": "2026-11-19T19:09:23.206732+00:00", "kind": "other", "label": "Updated", "source": "debian_tracker \u00b7 DEBIAN-CVE-2026-99472", "record": "DEBIAN-CVE-2026-99472", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-20T04:36:08.082Z", "anchors": {"origin": {"timestamp": "2026-11-19T14:42:59.997Z", "date_only": false, "value": "2026-11-19T14:42:59.997Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99472", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-19T14:42:59.997Z", "date_only": false, "value": "2026-11-19T14:42:59.997Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99472", "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": 49988.085691, "hours": 13.88557935861111, "days": 0.5785658066087963, "min_seconds": 49988.085691, "max_seconds": 49988.085691, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-19T14:42:59.997Z", "date_only": false, "value": "2026-11-19T14:42:59.997Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99472", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-20T04:36:08.082Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}
