PT-2026-151684

CVE-2026-99473

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾