{
  "id": "CVE-2026-99082",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-99082",
  "published_at": "2026-10-23T12:45:00.798Z",
  "title": "KVM: x86: Use active memslots for the per-vCPU MMIO cache",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 8.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Use active memslots for the per-vCPU MMIO cache\n\nKVM tags the per-vCPU MMIO cache with a memslot generation so that a\nmemslot update invalidates cached MMIO information.  Both the fill and\nvalidation paths use kvm_memslots(), which unconditionally selects address\nspace 0, even when the vCPU is running in SMM and using address space 1.\n\nCommit 56f17dd3fbc4 (\"kvm: x86: fix stale mmio cache bug\") added the\nmemslot generation to the cache key so that a memslot update could not\nleave a stale entry valid.  When commit 699023e23965 (\"KVM: x86: add SMM\nto the MMU role, support SMRAM address space\") added the SMM address space,\nthese helpers were not converted to use the active memslots.\n\nConsequently, an update to the SMM memslots can leave an entry from the old\nSMM address space apparently valid after the vCPU returns to the normal\naddress space.  A guest can then cause an access to valid RAM at the same\nGFN to be returned to userspace as KVM_EXIT_MMIO.\n\nCompleting that exit through the VMM's RAM address space writes the backing\npage without going through KVM's write-tracking path.  If the page backs a\nnested EPT table, KVM can continue using shadow translations derived from\nthe old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault()\ncatches this invalid cache and memslot combination.\n\nUse the vCPU's active memslots when caching and validating the entry.\nMemslot generations are unique across address spaces, so the generation\nalso distinguishes the normal and SMM views.  This matches the MMIO SPTE\ncache, which already uses kvm_vcpu_memslots().\n\nOn an unpatched current-mainline kernel, a regression test that fills the\ncache in SMM and updates only the SMM memslots fails the intended RAM write\nand triggers the kvm_mmu_write_protect_fault() warning.  With this change,\nthe same test completes the RAM write without a warning.  The x86/smm_test,\nset_memory_region_test, and memslot_modification_stress_test selftests also\npass.",
  "cvss_by_source": {
    "cna": 8.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 699023e239658e62da6f42f47d31b54788521ec1, \u003c 485a5286675b15b00ee850d90eaa178cc588445f",
          "\u003e= 699023e239658e62da6f42f47d31b54788521ec1, \u003c 445e3369ac8cc1b18aedc8e8f977c68a0a326fa9",
          "\u003e= 699023e239658e62da6f42f47d31b54788521ec1, \u003c 1c77d33d85786d36e56ca1b580fb55347fd65b47",
          "\u003e= 699023e239658e62da6f42f47d31b54788521ec1, \u003c a63f79d9da9468952396af73e1e53330845cf876",
          "\u003e= 699023e239658e62da6f42f47d31b54788521ec1, \u003c 7fd4e64f4bbc8c35ae8f0d2a1fb5b77a76d5b4fd",
          "\u003e= 699023e239658e62da6f42f47d31b54788521ec1, \u003c 2566780c684c9c21241d409d790087c73070f312",
          "\u003e= 699023e239658e62da6f42f47d31b54788521ec1, \u003c e792a9ace39d2812a5b342a1987186c7bc653204",
          "\u003e= 699023e239658e62da6f42f47d31b54788521ec1, \u003c b3e6212dea2e4328a841ceb37f377583176dc735"
        ],
        "fixed_in": [
          "485a5286675b15b00ee850d90eaa178cc588445f",
          "445e3369ac8cc1b18aedc8e8f977c68a0a326fa9",
          "1c77d33d85786d36e56ca1b580fb55347fd65b47",
          "a63f79d9da9468952396af73e1e53330845cf876",
          "7fd4e64f4bbc8c35ae8f0d2a1fb5b77a76d5b4fd",
          "2566780c684c9c21241d409d790087c73070f312",
          "e792a9ace39d2812a5b342a1987186c7bc653204",
          "b3e6212dea2e4328a841ceb37f377583176dc735"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "4.2"
        ],
        "fixed_in": [
          "0",
          "5.10.273",
          "5.15.224",
          "6.1.191",
          "6.6.160",
          "6.12.114",
          "6.18.58",
          "7.2.12",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 485a5286675b15b00ee850d90eaa178cc588445f or 445e3369ac8cc1b18aedc8e8f977c68a0a326fa9 or 1c77d33d85786d36e56ca1b580fb55347fd65b47 or a63f79d9da9468952396af73e1e53330845cf876 or 7fd4e64f4bbc8c35ae8f0d2a1fb5b77a76d5b4fd or 2566780c684c9c21241d409d790087c73070f312 or e792a9ace39d2812a5b342a1987186c7bc653204 or b3e6212dea2e4328a841ceb37f377583176dc735 or later.",
      "Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.160 or 6.12.114 or 6.18.58 or 7.2.12 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
