Skip to content
OpenAdvisories
Unscored CVE-2026-99335 EUVD-2026-130233GHSA-3w6g-cr7w-gq2g

KVM: guest_memfd: Establish memslot<=>guest_memfd bindings *after* memslot is ready

Published Nov 19, 2026 · Updated Nov 19, 2026 · Assigned by Linux

Description

In the Linux kernel, the following vulnerability has been resolved:

KVM: guest_memfd: Establish memslot<=>guest_memfd bindings *after* memslot is ready

Wait to bind a memslot to a guest_memfd instance until *after* the memslot
is fully prepared, as creating the binding in guest_memfd will effectively
expose the memslot to readers. As pointed out by Sashiko, binding the
memslot before it's ready to be exposed to the rest of the world can break
various memslot assumption and rules. E.g. x86 could observe a NULL rmap
pointer if a PUNCH_HOLE hit the guest_memfd after the binding was created,
but before KVM made it through kvm_prepare_memory_region().

Affected products

VendorProductAffectedFixed
Linux Linux 6.8 6.12.118

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 linux 7.3.3-1 —
Debian 13 linux No fix yet —

Advisories 1

References