CVE-2026-99473
In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Gracefully handle xarray errors when binding a memslo
CVSS
—
No CVSS
EPSS
—
KEV
—
Exploit Today
—
0-100
Published: Nov 19, 2026 · Last modified: Nov 19, 2026
Not enough EPSS history yet.
In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot If inserting a memslot into a guest_memfd's bindings xarray fails, propagate the error back to the caller, i.e. fail memslot creation as well. Signalling success and continuing on with memslot creation results in use-after-free, as the guest_memfd instance will remain reachable via the memslot after the file is freed (kvm_gmem_release() won't nullify the file pointer due to lack of a valid binding). Opportunistically WARN and reject binding if KVM_MEMSLOT_GMEM_ONLY is already set, partly to guard against goofs elsewhere, but mostly so that KVM doesn't need to worry about clobbering flags when unwinding on failure. Regarding the unwind, the slot must be fully prepared before inserting it into the bindings, at which point the slot becomes reachable. I.e. waiting to update the slot in order to avoid the ugly unwind isn't an option. And as part of the unwind, explicitly nullify the relevant bindings, as xarray can store a subset of entries when populating a range.
- git.kernel.orghttps://git.kernel.org/stable/c/1706461eb1af814366b6d0ab413edd0876bd8033
- git.kernel.orghttps://git.kernel.org/stable/c/2cfc1ccf67ffe96811c816d27d44128c5d5833ec
- git.kernel.orghttps://git.kernel.org/stable/c/2fa83c615f8dbb240b262265e788b120b6384e7b
- git.kernel.orghttps://git.kernel.org/stable/c/e6ecb88711d93b9e014532f17d3d29b57e80932c
No related CVEs by CWE or product.