Skip to content
Threat Brief

← All advisories

CVE-2026-99082

High 8.8No known exploitationFix available

KVM: x86: Use active memslots for the per-vCPU MMIO cache

Record last updated

CVSS score

8.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 5% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use active memslots for the per-vCPU MMIO cache KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO information. Both the fill and validation paths use kvm_memslots(), which unconditionally selects address space 0, even when the vCPU is running in SMM and using address space 1. Commit 56f17dd3fbc4 ("kvm: x86: fix stale mmio cache bug") added the memslot generation to the cache key so that a memslot update could not leave a stale entry valid. When commit 699023e23965 ("KVM: x86: add SMM to the MMU role, support SMRAM address space") added the SMM address space, these helpers were not converted to use the active memslots. Consequently, an update to the SMM memslots can leave an entry from the old SMM address space apparently valid after the vCPU returns to the normal address space. A guest can then cause an access to valid RAM at the same GFN to be returned to userspace as KVM_EXIT_MMIO. Completing that exit through the VMM's RAM address space writes the backing page without going through KVM's write-tracking path. If the page backs a nested EPT table, KVM can continue using shadow translations derived from the old contents. The WARN_ON_ONCE() in kvm_mmu_write_protect_fault() catches this invalid cache and memslot combination. Use the vCPU's active memslots when caching and validating the entry. Memslot generations are unique across address spaces, so the generation also distinguishes the normal and SMM views. This matches the MMIO SPTE cache, which already uses kvm_vcpu_memslots(). On an unpatched current-mainline kernel, a regression test that fills the cache in SMM and updates only the SMM memslots fails the intended RAM write and triggers the kvm_mmu_write_protect_fault() warning. With this change, the same test completes the RAM write without a warning. The x86/smm_test, set_memory_region_test, and memslot_modification_stress_test selftests also pass.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 699023e239658e62da6f42f47d31b54788521ec1 before 7fd4e64f4bbc8c35ae8f0d2a1fb5b77a76d5b4fd7fd4e64f4bbc8c35ae8f0d2a1fb5b77a76d5b4fdCVE Program
LinuxLinuxfrom 699023e239658e62da6f42f47d31b54788521ec1 before 1c77d33d85786d36e56ca1b580fb55347fd65b471c77d33d85786d36e56ca1b580fb55347fd65b47CVE Program
LinuxLinuxfrom 699023e239658e62da6f42f47d31b54788521ec1 before a63f79d9da9468952396af73e1e53330845cf876a63f79d9da9468952396af73e1e53330845cf876CVE Program
LinuxLinuxfrom 699023e239658e62da6f42f47d31b54788521ec1 before 2566780c684c9c21241d409d790087c73070f3122566780c684c9c21241d409d790087c73070f312CVE Program
LinuxLinuxfrom 699023e239658e62da6f42f47d31b54788521ec1 before b3e6212dea2e4328a841ceb37f377583176dc735b3e6212dea2e4328a841ceb37f377583176dc735CVE Program
LinuxLinuxfrom 699023e239658e62da6f42f47d31b54788521ec1 before e792a9ace39d2812a5b342a1987186c7bc653204e792a9ace39d2812a5b342a1987186c7bc653204CVE Program
LinuxLinuxfrom 699023e239658e62da6f42f47d31b54788521ec1 before 485a5286675b15b00ee850d90eaa178cc588445f485a5286675b15b00ee850d90eaa178cc588445fCVE Program
LinuxLinuxfrom 699023e239658e62da6f42f47d31b54788521ec1 before 445e3369ac8cc1b18aedc8e8f977c68a0a326fa9445e3369ac8cc1b18aedc8e8f977c68a0a326fa9CVE Program
LinuxLinux4.2Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.159.1-1 on Azure Linux 3.0Not documented6.6.161.1-1Microsoft MSRC
Microsoftazl4 kernel 6.18.57-1.12.azl4 on Azure Linux 4.0Not documented0:6.18.62-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 5.10.273 up to and including 5.10.*Not documentedCVE Program
LinuxLinux (unaffected)from 5.15.224 up to and including 5.15.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.1.191 up to and including 6.1.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.114 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.58 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.160 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.12 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.2Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Advisory change

    Microsoft advisory revised (7.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  9. Advisory change

    Microsoft advisory revised (8.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  10. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references