Linux kernel denial of service via unbounded page table lists in KVM MMU
- Exploited
- No known exploitation
- Fix
- Fixed in 6.12.118, 6.18.64, 7.3.5
- Who is exposed
- Not reported
Summary
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.
What to do
Upgrade to a fixed version: 6.12.118, 6.18.64, 7.3.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99710 (KVM: x86/mmu: Cap number of parent PTEs per SP at 1000 (the arbitrary rmap limit)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99710 (entry last updated 2026-11-20):
Affected:
- Linux Linux: fixed in 6.12.118; fixed in 6.18.64; fixed in 7.3.5
- Linux Linux: from 6.19, fixed in 7.3.5; from 6.13, fixed in 6.18.64; fixed in 6.12.118
Fixed versions: 6.12.118, 6.18.64, 7.3.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99710 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99710 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/edf87e07376054eedcd5306e0794a26e3004d97b
- https://git.kernel.org/stable/c/e0752f3e543c1b67fc9115251ae6b8f151ba9f04
- https://git.kernel.org/stable/c/72238066aacc400df69cef4b602f083ae4737762
- https://git.kernel.org/stable/c/e4558c3d7198ed9a0adc3304681f561f4e4d80e1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99710
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99710"}.Affected versions
- Linux Linuxfixed in 6.12.118; fixed in 6.18.64; fixed in 7.3.5
- Linux LinuxFrom 6.19 · fixed in 7.3.5; From 6.13 · fixed in 6.18.64; fixed in 6.12.118
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99710 |
| Record | NVD · CVE-2026-99710 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/edf87e07376054eedcd5306e0794a26e3004d97b |
| Link | git.kernel.org · stable/c/e0752f3e543c1b67fc9115251ae6b8f151ba9f04 |
| Link | git.kernel.org · stable/c/72238066aacc400df69cef4b602f083ae4737762 |
| Link | git.kernel.org · stable/c/e4558c3d7198ed9a0adc3304681f561f4e4d80e1 |
Questions about CVE-2026-99710
Is CVE-2026-99710 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99710?
Linux: before 6.12.118; before 6.18.64; before 7.3.5. Linux: from 6.19 before 7.3.5; from 6.13 before 6.18.64; before 6.12.118.
Source: cve.now feed data
How do I fix CVE-2026-99710?
Upgrade to a fixed version: 6.12.118, 6.18.64, 7.3.5.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.