{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-99710","id":"CVE-2026-99710","title":"Linux kernel denial of service in KVM shadow page reverse mappings","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Cap number of parent PTEs per SP at 1000 (the arbitrary rmap limit)\n\nWhen potentially reusing a shadow page, zap the shadow page if its number\nof parent PTEs exceeds KVM's (mostly) arbitrary rmap recycling threshold.\nLetting the guest create a (mostly) unbounded number of parent PTEs allows\nthe guest to coerce KVM i","descriptionLong":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Cap number of parent PTEs per SP at 1000 (the arbitrary rmap limit)\n\nWhen potentially reusing a shadow page, zap the shadow page if its number\nof parent PTEs exceeds KVM's (mostly) arbitrary rmap recycling threshold.\nLetting the guest create a (mostly) unbounded number of parent PTEs allows\nthe guest to coerce KVM into creating lists containing millions of PTEs,\neffectively bounded only by the maximum number of shadow pages.\n\nBecause PTE lists are simple singly linked lists, removal is O(n).  Even\nworse, if a list is constructed just so, teardown can be O(n^2), e.g. if\nSPTEs are built such that zapping child SPTEs always zaps the last entry\nin the list.  To cap things off, all paths that walk PTE lists do so\nwhile holding mmu_lock, without conditionally rescheduling.\n\nUsing a doubly linked list would not address the issue, as removal would\nremain O(n) since KVM still wouldn't know where in the list to remove from.\nRemoval could be made O(1) by storing a per-SPTE pointer, but that would\nlargely defeat the purpose of reusing SPs, and would penalize well-behaved\nguests, especially for nested TDP where aliasing page tables is uncommon.\n\nSo, cap the maximum number of parent PTEs at the rmap limit.  In practice,\nwell-behaved guests will likely never run afoul of the limit.  E.g. when\nrunning Linux as L1 with TDP, the number of parent PTEs for a single SP\ntops out at under 200 (though undoubtedly obscure workloads can push it\nhigher).  Deliberately use a \"greater than or equal\" as opposed to rmap's\nstrictly \"greater than\", as the rmap code checks the threshold immediately\n*after* inserting into the list, i.e. the limit is 1000 for rmaps, KVM just\nvery briefly blows past it.\n\nApply the check to both indirect and direct SPs, because while a fully\ndirect MMU naturally limits the number of parent PTEs to '1', direct SPs in\nindirect MMUs have no such constraint.  E.g. if the guest maps a huge PTE\ninto many locations in its page tables, and KVM is backing the hugepage\nwith a direct SP, i.e. with a series of smaller pages, then KVM could end\nup with a direct SP with many parents.\n\nNote, shadow_mmu_try_split_huge_pages() always restarts the rmap walk or\nbails entirely if it gets to the point where it tries to grab a SP, i.e.\nthere is *no* pre-existing bug that would be tripped by zapping a SP and\nthus rmaps when getting a SP.","published":"2026-11-20T05:50:50.082Z","updated":"2026-11-20T05:50:50.082Z","reserved":"2026-09-25T10:25:14.430Z","status":"PUBLISHED","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"edf87e07376054eedcd5306e0794a26e3004d97b","status":"affected","versionType":"git"},{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"e0752f3e543c1b67fc9115251ae6b8f151ba9f04","status":"affected","versionType":"git"},{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"72238066aacc400df69cef4b602f083ae4737762","status":"affected","versionType":"git"},{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"e4558c3d7198ed9a0adc3304681f561f4e4d80e1","status":"affected","versionType":"git"},{"version":"0","lessThan":"6.12.118","status":"affected","versionType":"semver"},{"version":"0","lessThan":"6.18.64","status":"affected","versionType":"semver"},{"version":"0","lessThan":"7.3.5","status":"affected","versionType":"semver"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.12.118","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.64","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.5","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/edf87e07376054eedcd5306e0794a26e3004d97b","tags":[]},{"url":"https://git.kernel.org/stable/c/e0752f3e543c1b67fc9115251ae6b8f151ba9f04","tags":[]},{"url":"https://git.kernel.org/stable/c/72238066aacc400df69cef4b602f083ae4737762","tags":[]},{"url":"https://git.kernel.org/stable/c/e4558c3d7198ed9a0adc3304681f561f4e4d80e1","tags":[]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":null,"epssPercentile":null,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-99710","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99710","ok":false,"note":"not found"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-99710","ok":false,"note":"no open-source package data"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-99710","ok":false,"note":"no score yet"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}