Skip to content

Commit eb5c99a

Browse files
sean-jcPlaidCat
authored andcommitted
KVM: x86: Fix shadow paging use-after-free due to unexpected GFN
jira VULN-186744 cve CVE-2026-46113 commit-author Sean Christopherson <seanjc@google.com> commit 0cb2af2 upstream-diff | Two adaptations were required for this tree: 1. spte_to_child_sp() does not exist here. Applying the upstream fix verbatim failed to build ("implicit declaration of function 'spte_to_child_sp'", -Werror). That helper was introduced upstream by 285f646 ("KVM: x86/mmu: Add helper to convert SPTE value to its shadow page"), an unrelated helper-relocation refactor that does not apply cleanly here; rather than pull it in, the call is written using this tree's existing equivalent. spte_to_child_sp(x) is defined upstream as to_shadow_page(x & SPTE_BASE_ADDR_MASK), which this tree already uses verbatim, so the substitution is functionally identical. 2. The upstream commit deletes drop_large_spte(), converting its sole caller to mmu_page_zap_pte() in __link_shadow_page(). This tree's drop_large_spte() differs cosmetically (WARN_ON / kvm_flush_remote_tlbs_with_address() vs the later WARN_ON_ONCE / kvm_flush_remote_tlbs_sptep() forms), so the deletion hunk did not apply automatically; the function is removed by hand. The caller conversion applied cleanly and no other references remain. No functional difference from upstream. The shadow MMU computes GFNs for direct shadow pages using sp->gfn plus the SPTE index. This assumption breaks for shadow paging if the guest page tables are modified between VM entries (similar to commit aad885e, "KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE", 2026-03-27). The flow is as follows: - a PDE is installed for a 2MB mapping, and a page in that area is accessed. KVM creates a kvm_mmu_page consisting of 512 4KB pages; the kvm_mmu_page is marked by FNAME(fetch) as direct-mapped because the guest's mapping is a huge page (and thus contiguous). - the PDE mapping is changed from outside the guest. - the guest accesses another page in the same 2MB area. KVM installs a new leaf SPTE and rmap entry; the SPTE uses the "correct" GFN (i.e. based on the new mapping, as changed in the previous step) but that GFN is outside of the [sp->gfn, sp->gfn + 511] range; therefore the rmap entry cannot be found and removed when the kvm_mmu_page is zapped. - the memslot that covers the first 2MB mapping is deleted, and the kvm_mmu_page for the now-invalid GPA is zapped. However, rmap_remove() only looks at the [sp->gfn, sp->gfn + 511] range established in step 1, and fails to find the rmap entry that was recorded by step 3. - any operation that causes an rmap walk for the same page accessed by step 3 then walks a stale rmap and dereferences a freed kvm_mmu_page. This includes dirty logging or MMU notifier invalidations (e.g., from MADV_DONTNEED). The underlying issue is that KVM's walking of shadow PTEs assumes that if a SPTE is present when KVM wants to install a non-leaf SPTE, then the existing kvm_mmu_page must be for the correct gfn. Because the only way for the gfn to be wrong is if KVM messed up and failed to zap a SPTE... which shouldn't happen, but *actually* only happens in response to a guest write. That bug dates back literally forever, as even the first version of KVM assumes that the GFN matches and walks into the "wrong" shadow page. However, that was only an imprecision until 2032a93 ("KVM: MMU: Don't allocate gfns page for direct mmu pages") came along. Fix it by checking for a target gfn mismatch and zapping the existing SPTE. That way the old SP and rmap entries are gone, KVM installs the rmap in the right location, and everyone is happy. Fixes: 2032a93 ("KVM: MMU: Don't allocate gfns page for direct mmu pages") Fixes: 6aa8b73 ("kvm: userspace interface") Reported-by: Alexander Bulekov <bkov@amazon.com> Reported-by: Fred Griffoul <fgriffo@amazon.co.uk> Cc: stable@vger.kernel.org Signed-off-by: Sean Christopherson <seanjc@google.com> Link: https://patch.msgid.link/20260503201029.106481-1-pbonzini@redhat.com/ Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> (cherry picked from commit 0cb2af2) Signed-off-by: Shreeya Patel <spatel@ciq.com>
1 parent ce60197 commit eb5c99a

1 file changed

Lines changed: 14 additions & 22 deletions

File tree

arch/x86/kvm/mmu/mmu.c

Lines changed: 14 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,8 @@ struct kmem_cache *mmu_page_header_cache;
167167
static struct percpu_counter kvm_total_used_mmu_pages;
168168

169169
static void mmu_spte_set(u64 *sptep, u64 spte);
170+
static int mmu_page_zap_pte(struct kvm *kvm, struct kvm_mmu_page *sp,
171+
u64 *spte, struct list_head *invalid_list);
170172

171173
struct kvm_mmu_role_regs {
172174
const unsigned long cr0;
@@ -1146,20 +1148,6 @@ static void drop_spte(struct kvm *kvm, u64 *sptep)
11461148
rmap_remove(kvm, sptep);
11471149
}
11481150

1149-
static void drop_large_spte(struct kvm *kvm, u64 *sptep, bool flush)
1150-
{
1151-
struct kvm_mmu_page *sp;
1152-
1153-
sp = sptep_to_sp(sptep);
1154-
WARN_ON(sp->role.level == PG_LEVEL_4K);
1155-
1156-
drop_spte(kvm, sptep);
1157-
1158-
if (flush)
1159-
kvm_flush_remote_tlbs_with_address(kvm, sp->gfn,
1160-
KVM_PAGES_PER_HPAGE(sp->role.level));
1161-
}
1162-
11631151
/*
11641152
* Write-protect on the specified @sptep, @pt_protect indicates whether
11651153
* spte write-protection is caused by protecting shadow page table.
@@ -2231,7 +2219,8 @@ static struct kvm_mmu_page *kvm_mmu_get_child_sp(struct kvm_vcpu *vcpu,
22312219
{
22322220
union kvm_mmu_page_role role;
22332221

2234-
if (is_shadow_present_pte(*sptep) && !is_large_pte(*sptep))
2222+
if (is_shadow_present_pte(*sptep) && !is_large_pte(*sptep) &&
2223+
to_shadow_page(*sptep & SPTE_BASE_ADDR_MASK) && to_shadow_page(*sptep & SPTE_BASE_ADDR_MASK)->gfn == gfn)
22352224
return ERR_PTR(-EEXIST);
22362225

22372226
role = kvm_mmu_child_role(sptep, direct, access);
@@ -2309,13 +2298,16 @@ static void __link_shadow_page(struct kvm *kvm,
23092298

23102299
BUILD_BUG_ON(VMX_EPT_WRITABLE_MASK != PT_WRITABLE_MASK);
23112300

2312-
/*
2313-
* If an SPTE is present already, it must be a leaf and therefore
2314-
* a large one. Drop it, and flush the TLB if needed, before
2315-
* installing sp.
2316-
*/
2317-
if (is_shadow_present_pte(*sptep))
2318-
drop_large_spte(kvm, sptep, flush);
2301+
if (is_shadow_present_pte(*sptep)) {
2302+
struct kvm_mmu_page *parent_sp;
2303+
LIST_HEAD(invalid_list);
2304+
2305+
parent_sp = sptep_to_sp(sptep);
2306+
WARN_ON_ONCE(parent_sp->role.level == PG_LEVEL_4K);
2307+
2308+
mmu_page_zap_pte(kvm, parent_sp, sptep, &invalid_list);
2309+
kvm_mmu_remote_flush_or_zap(kvm, &invalid_list, true);
2310+
}
23192311

23202312
spte = make_nonleaf_spte(sp->spt, sp_ad_disabled(sp));
23212313

0 commit comments

Comments
 (0)