{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "b9220d32799a62c634f7b0b3618da52772626952"
            },
            {
              "fixed": "fabc002f6396202b5ad7ad4ceec24d27aad90f3f"
            },
            {
              "fixed": "da260bcb56feeb6489a83f310308453a0a7de25e"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.9.0"
            },
            {
              "fixed": "7.3.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99472.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: pfncache: use a dedicated invalidation sequence for cache refresh\n\nThe gfn_to_pfn_cache refresh path guards against mmu notifier\ninvalidations which complete while it has dropped gpc-\u003elock for the\nHVA-\u003ePFN lookup: hva_to_pfn_retry() samples kvm-\u003emmu_invalidate_seq\nand retries if it changed, or if mn_active_invalidate_count is still\nelevated.\n\nThat is insufficient for HVA-based caches. mmu_invalidate_seq is only\nadvanced by kvm_mmu_invalidate_end() when the invalidated range\noverlaps a memslot, and an HVA-based cache (e.g. the Xen shared_info\npage mapped with KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA) need not be backed\nby any memslot at all. An invalidation of the cached HVA which starts\nand ends entirely within the lookup window is thus invisible to the\nretry check: mn_active_invalidate_count is back to zero and the\nsequence never moved. The refresh then publishes a mapping of a page\nwhich has already been freed, and the next reader dereferences it:\n\n  BUG: KASAN: use-after-free in kvm_xen_shared_info_init+0x3c6/0x440\n  Read of size 4 at addr ffff8880599c2900 by task syz.2.383/7257\n\nSince gfn_to_pfn_cache_invalidate_start() deliberately skips caches\nwhich are not currently valid (including one whose refresh is in\nprogress, as the refresh clears the valid flag before dropping the\nlock), the retry check is the only line of defence, and it must fire\nfor *any* invalidation, not just those hitting a memslot.\n\nAdd a dedicated kvm-\u003egpc_invalidate_seq, incremented by every\nkvm_mmu_notifier_invalidate_range_end() under mn_invalidate_lock\nbefore mn_active_invalidate_count is decremented, and check it in\nhva_to_pfn_retry() instead of mmu_invalidate_seq. Incrementing in\nrange_end() in the same critical section as the in-progress count\nalso closes the variant where the cache is activated with the\ncontested HVA only after invalidate_range_start() has run.\n\nThe same bug is also reachable through the per-vCPU vcpu_info cache\n(KVM_XEN_VCPU_ATTR_TYPE_VCPU_INFO_HVA), where the stale mapping is\nthen dereferenced by kvm_setup_guest_pvclock() on the next KVM_RUN:\n\n  BUG: KASAN: use-after-free in kvm_setup_guest_pvclock+0x5bf/0x660\n\nThis intentionally makes refresh retry on *unrelated* mmu notifier\nevents; restoring precision (and reworking the GPC locking more\ngenerally) is left for a subsequent series.\n\nReproducers: https://david.woodhou.se/xen_shinfo_race.c\n             https://david.woodhou.se/vcpu_info_race.c",
  "id": "CVE-2026-99472",
  "modified": "2026-11-19T16:45:49.778806426Z",
  "published": "2026-11-19T14:42:59.997Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/da260bcb56feeb6489a83f310308453a0a7de25e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fabc002f6396202b5ad7ad4ceec24d27aad90f3f"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99472.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99472"
    }
  ],
  "schema_version": "1.9.2",
  "summary": "KVM: pfncache: use a dedicated invalidation sequence for cache refresh"
}