Skip to content
Threat Brief

← All advisories

CVE-2026-99710

Severity unknownNo known exploitationFix available

KVM: x86/mmu: Cap number of parent PTEs per SP at 1000 (the arbitrary rmap limit)

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% 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/mmu: Cap number of parent PTEs per SP at 1000 (the arbitrary rmap limit) When potentially reusing a shadow page, zap the shadow page if its number of parent PTEs exceeds KVM's (mostly) arbitrary rmap recycling threshold. Letting the guest create a (mostly) unbounded number of parent PTEs allows the guest to coerce KVM into creating lists containing millions of PTEs, effectively bounded only by the maximum number of shadow pages. Because PTE lists are simple singly linked lists, removal is O(n). Even worse, if a list is constructed just so, teardown can be O(n^2), e.g. if SPTEs are built such that zapping child SPTEs always zaps the last entry in the list. To cap things off, all paths that walk PTE lists do so while holding mmu_lock, without conditionally rescheduling. Using a doubly linked list would not address the issue, as removal would remain O(n) since KVM still wouldn't know where in the list to remove from. Removal could be made O(1) by storing a per-SPTE pointer, but that would largely defeat the purpose of reusing SPs, and would penalize well-behaved guests, especially for nested TDP where aliasing page tables is uncommon. So, cap the maximum number of parent PTEs at the rmap limit. In practice, well-behaved guests will likely never run afoul of the limit. E.g. when running Linux as L1 with TDP, the number of parent PTEs for a single SP tops out at under 200 (though undoubtedly obscure workloads can push it higher). Deliberately use a "greater than or equal" as opposed to rmap's strictly "greater than", as the rmap code checks the threshold immediately *after* inserting into the list, i.e. the limit is 1000 for rmaps, KVM just very briefly blows past it. Apply the check to both indirect and direct SPs, because while a fully direct MMU naturally limits the number of parent PTEs to '1', direct SPs in indirect MMUs have no such constraint. E.g. if the guest maps a huge PTE into many locations in its page tables, and KVM is backing the hugepage with a direct SP, i.e. with a series of smaller pages, then KVM could end up with a direct SP with many parents. Note, shadow_mmu_try_split_huge_pages() always restarts the rmap walk or bails entirely if it gets to the point where it tries to grab a SP, i.e. there is *no* pre-existing bug that would be tripped by zapping a SP and thus rmaps when getting a SP.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before edf87e07376054eedcd5306e0794a26e3004d97bedf87e07376054eedcd5306e0794a26e3004d97bCVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before e0752f3e543c1b67fc9115251ae6b8f151ba9f04e0752f3e543c1b67fc9115251ae6b8f151ba9f04CVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 72238066aacc400df69cef4b602f083ae473776272238066aacc400df69cef4b602f083ae4737762CVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before e4558c3d7198ed9a0adc3304681f561f4e4d80e1e4558c3d7198ed9a0adc3304681f561f4e4d80e1CVE Program
LinuxLinuxall versions before 6.12.1186.12.118CVE Program
LinuxLinuxall versions before 6.18.646.18.64CVE Program
LinuxLinuxall versions before 7.3.57.3.5CVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references