CVE-2026-99472 (GCVE-0-2026-99472)

Vulnerability from cvelistv5 – Published: 2026-11-19 14:42 – Updated: 2026-11-19 14:42
VLAI
Title
KVM: pfncache: use a dedicated invalidation sequence for cache refresh
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: pfncache: use a dedicated invalidation sequence for cache refresh The gfn_to_pfn_cache refresh path guards against mmu notifier invalidations which complete while it has dropped gpc->lock for the HVA->PFN lookup: hva_to_pfn_retry() samples kvm->mmu_invalidate_seq and retries if it changed, or if mn_active_invalidate_count is still elevated. That is insufficient for HVA-based caches. mmu_invalidate_seq is only advanced by kvm_mmu_invalidate_end() when the invalidated range overlaps a memslot, and an HVA-based cache (e.g. the Xen shared_info page mapped with KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA) need not be backed by any memslot at all. An invalidation of the cached HVA which starts and ends entirely within the lookup window is thus invisible to the retry check: mn_active_invalidate_count is back to zero and the sequence never moved. The refresh then publishes a mapping of a page which has already been freed, and the next reader dereferences it: 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 Since gfn_to_pfn_cache_invalidate_start() deliberately skips caches which are not currently valid (including one whose refresh is in progress, as the refresh clears the valid flag before dropping the lock), the retry check is the only line of defence, and it must fire for *any* invalidation, not just those hitting a memslot. Add a dedicated kvm->gpc_invalidate_seq, incremented by every kvm_mmu_notifier_invalidate_range_end() under mn_invalidate_lock before mn_active_invalidate_count is decremented, and check it in hva_to_pfn_retry() instead of mmu_invalidate_seq. Incrementing in range_end() in the same critical section as the in-progress count also closes the variant where the cache is activated with the contested HVA only after invalidate_range_start() has run. The same bug is also reachable through the per-vCPU vcpu_info cache (KVM_XEN_VCPU_ATTR_TYPE_VCPU_INFO_HVA), where the stale mapping is then dereferenced by kvm_setup_guest_pvclock() on the next KVM_RUN: BUG: KASAN: use-after-free in kvm_setup_guest_pvclock+0x5bf/0x660 This intentionally makes refresh retry on *unrelated* mmu notifier events; restoring precision (and reworking the GPC locking more generally) is left for a subsequent series. Reproducers: https://david.woodhou.se/xen_shinfo_race.c https://david.woodhou.se/vcpu_info_race.c
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 7143 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: b9220d32799a62c634f7b0b3618da52772626952 , < fabc002f6396202b5ad7ad4ceec24d27aad90f3f (git)
Affected: b9220d32799a62c634f7b0b3618da52772626952 , < da260bcb56feeb6489a83f310308453a0a7de25e (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.9
Unaffected: 0 , < 6.9 (semver)
Unaffected: 7.3.2 , ≤ 7.3.* (semver)
Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "include/linux/kvm_host.h",
            "virt/kvm/kvm_main.c",
            "virt/kvm/pfncache.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "fabc002f6396202b5ad7ad4ceec24d27aad90f3f",
              "status": "affected",
              "version": "b9220d32799a62c634f7b0b3618da52772626952",
              "versionType": "git"
            },
            {
              "lessThan": "da260bcb56feeb6489a83f310308453a0a7de25e",
              "status": "affected",
              "version": "b9220d32799a62c634f7b0b3618da52772626952",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "include/linux/kvm_host.h",
            "virt/kvm/kvm_main.c",
            "virt/kvm/pfncache.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.9"
            },
            {
              "lessThan": "6.9",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.3.*",
              "status": "unaffected",
              "version": "7.3.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.4-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3.2",
                  "versionStartIncluding": "6.9",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.4-rc1",
                  "versionStartIncluding": "6.9",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-19T14:42:59.997Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/fabc002f6396202b5ad7ad4ceec24d27aad90f3f"
        },
        {
          "url": "https://git.kernel.org/stable/c/da260bcb56feeb6489a83f310308453a0a7de25e"
        }
      ],
      "title": "KVM: pfncache: use a dedicated invalidation sequence for cache refresh",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-99472",
    "datePublished": "2026-11-19T14:42:59.997Z",
    "dateReserved": "2026-09-25T10:25:14.417Z",
    "dateUpdated": "2026-11-19T14:42:59.997Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-99472",
      "date": "2026-11-20",
      "epss": "0.00163",
      "percentile": "0.05597"
    },
    "microsoft_vex": {
      "current_release_date": "2026-11-20T01:10:37.000Z",
      "cve": "CVE-2026-99472",
      "id": "msrc_CVE-2026-99472",
      "initial_release_date": "2026-11-20T01:10:37.000Z",
      "product_status:under_investigation": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "KVM: pfncache: use a dedicated invalidation sequence for cache refresh",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-99472.json",
      "version": "1"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "include/linux/kvm_host.h",
                  "virt/kvm/kvm_main.c",
                  "virt/kvm/pfncache.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "fabc002f6396202b5ad7ad4ceec24d27aad90f3f",
                    "status": "affected",
                    "version": "b9220d32799a62c634f7b0b3618da52772626952",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "da260bcb56feeb6489a83f310308453a0a7de25e",
                    "status": "affected",
                    "version": "b9220d32799a62c634f7b0b3618da52772626952",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "include/linux/kvm_host.h",
                  "virt/kvm/kvm_main.c",
                  "virt/kvm/pfncache.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "6.9"
                  },
                  {
                    "lessThan": "6.9",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.3.*",
                    "status": "unaffected",
                    "version": "7.3.2",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.4-rc1",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "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",
        "lastModified": "2026-11-19T15:18:01.633",
        "metrics": {},
        "published": "2026-11-19T15:18:01.633",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/da260bcb56feeb6489a83f310308453a0a7de25e"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/fabc002f6396202b5ad7ad4ceec24d27aad90f3f"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-19T21:39:05+00:00",
      "cve": "CVE-2026-99472",
      "id": "CVE-2026-99472",
      "initial_release_date": "2026-11-19T14:42:59.997000+00:00",
      "product_status:known_not_affected": "204",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: kernel: KVM: denial of service via use-after-free in pfncache",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99472.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.