CVE-2026-53359

published 4 Jul 2026 · updated 3 Oct 2026

KVM: x86: Fix shadow paging use-after-free due to unexpected role

9.8CriticalCVSS 8.8EPSS 1%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 0b5e8ead71e683bcf6232db16234cf7e6d553a23, Kernel 1ae7d5a6db6c190ce183e3098ca0e0846e14d462, Kernel 2ad3afa40ac6aa340dada122f9abfa46c0a6eb35 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected role Commit 0cb2af2ea66ad ("KVM: x86: Fix shadow paging use-after-free due to unexpected GFN") fixed a shadow paging mismatch between stored and computed GFNs; the bug could be triggered by changing a PDE mapping from outside the guest, and then deleting a memslot. The rmap_remove() call would miss entries created after the PDE change because the GFN of the leaf SPTE does not match the GFN of the struct kvm_mmu_page. A similar hole however remains if the modified PDE points to a non-leaf page. In this case the gfn can be made to match, but the role does not match: the original large 2MB page creates a kvm_mmu_page with direct=1, while the new 4KB needs a kvm_mmu_page with direct=0. However, kvm_mmu_get_child_sp() does not compare the role, and therefore reuses the page. The next step is installing a leaf (4KB) SPTE on the new path which records an rmap entry under the gfn resolved by the walk. But when that child is zapped its parent kvm_mmu_page has direct=1 and kvm_mmu_page_get_gfn() computes the gfn for the 4KB page as sp->gfn + index instead of using sp->shadowed_translation[] (or sp->gfns[] in older kernels). It therefore fails to remove the recorded entry. When the memslot is dropped the shadow page is freed but the rmap entry survives, as in the scenario that was already fixed. Code that later walks that gfn (dirty logging, MMU notifier invalidation, and so on) dereferences an sptep that lies in the freed page, causing the use-after-free.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.36, >=2032a93d66fa282ba0f2ea9152eeff9511fa9a96 <0b5e8ead71e683bcf6232db16234cf7e6d553a23, >=2032a93d66fa282ba0f2ea9152eeff9511fa9a96 <1ae7d5a6db6c190ce183e3098ca0e0846e14d462, >=2032a93d66fa282ba0f2ea9152eeff9511fa9a96 <2ad3afa40ac6aa340dada122f9abfa46c0a6eb35, >=2032a93d66fa282ba0f2ea9152eeff9511fa9a96 <5e470998a23e4c3d89ed24e8172cb22747e61efa, >=2032a93d66fa282ba0f2ea9152eeff9511fa9a96 <81ccda30b4e83d8f5cc4fd50503c44e3a33abfeb, >=2032a93d66fa282ba0f2ea9152eeff9511fa9a96 <9291654d69e08542de37755cebe4d5b02c3170d1, >=2032a93d66fa282ba0f2ea9152eeff9511fa9a96 <b1337aae5e194324e4810d561764e7793f8b38640b5e8ead71e683bcf6232db16234cf7e6d553a23, 1ae7d5a6db6c190ce183e3098ca0e0846e14d462, 2ad3afa40ac6aa340dada122f9abfa46c0a6eb35, 5e470998a23e4c3d89ed24e8172cb22747e61efa, 81ccda30b4e83d8f5cc4fd50503c44e3a33abfeb, 9291654d69e08542de37755cebe4d5b02c3170d1, b1337aae5e194324e4810d561764e7793f8b3864

Exploit evidence

1 public sources

Coverage

News and research mentioning this CVE

Research blogs·research

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-53359 severity on Zeptric[![CVE-2026-53359](https://zeptric.io/badge/cve/CVE-2026-53359.svg)](https://zeptric.io/cve/CVE-2026-53359)