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
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
a7800aa80ea4d5356b8474c2302812e9d4926fa6 to < 698f807aa8df9414fdc23d9ea454f4883b5b08ffaffecteda7800aa80ea4d5356b8474c2302812e9d4926fa6 to < dc0cb5d30647b22a3da252a2847ed8f6afb5d567affecteda7800aa80ea4d5356b8474c2302812e9d4926fa6 to < fd224f1778e13660aec4e1f51fcdaeab5794e7eeaffecteda7800aa80ea4d5356b8474c2302812e9d4926fa6 to < 3fe5d2944e5ac3fc5073344b0982c73703332e18affected
Linux Linux
Default version status: affected
6.8affected0 to < 6.8unaffected6.12.118 to ≤ 6.12.*unaffected6.18.64 to ≤ 6.18.*unaffected7.3.2 to ≤ 7.3.*unaffected7.4-rc1 to ≤ *unaffected