KVM: Harden kvm_vcpu_map() against double-mapping and thus leaking references

Now that all on-stack maps use CLASS(kvm_vcpu_map_local), i.e. now that all
maps are zero-allocated, explicitly put any existing mappings/references
when establishing a new mapping to harden against KVM bugs leaking memory,
but yell loudly as the owner of the map is still ultimately responsible for
the lifecycle of the mapping.

Suggested-by: Yosry Ahmed <yosry@kernel.org>
Link: https://patch.msgid.link/20260724004757.131420-7-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
This commit is contained in:
Sean Christopherson
2026-07-23 17:47:57 -07:00
parent e060b94a1c
commit e186d4e34a

View File

@@ -3118,6 +3118,9 @@ int __kvm_vcpu_map(struct kvm_vcpu *vcpu, gfn_t gfn, struct kvm_host_map *map,
.pin = true,
};
if (WARN_ON_ONCE(map->hva))
kvm_vcpu_unmap(vcpu, map);
map->pinned_page = NULL;
map->page = NULL;
map->hva = NULL;