KVM: guest_memfd: Establish memslot<=>guest_memfd bindings *after* memslot is ready
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fd224f1778e13660aec4e1f51fcdaeab5794e7ee, Kernel 3fe5d2944e5ac3fc5073344b0982c73703332e18, Kernel 698f807aa8df9414fdc23d9ea454f4883b5b08ff and 4 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=a7800aa80ea4d5356b8474c2302812e9d4926fa6 <fd224f1778e13660aec4e1f51fcdaeab5794e7ee, >=a7800aa80ea4d5356b8474c2302812e9d4926fa6 <3fe5d2944e5ac3fc5073344b0982c73703332e18, >=a7800aa80ea4d5356b8474c2302812e9d4926fa6 <698f807aa8df9414fdc23d9ea454f4883b5b08ff, >=a7800aa80ea4d5356b8474c2302812e9d4926fa6 <dc0cb5d30647b22a3da252a2847ed8f6afb5d567, =6.8 | fd224f1778e13660aec4e1f51fcdaeab5794e7ee, 3fe5d2944e5ac3fc5073344b0982c73703332e18, 698f807aa8df9414fdc23d9ea454f4883b5b08ff, dc0cb5d30647b22a3da252a2847ed8f6afb5d567 |
| linux-kernel: Kernel | >=6.19.0 <7.3.2, >=6.8.0 <6.12.118, >=6.13.0 <6.18.64 | 7.3.2, 6.12.118, 6.18.64 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket