PT-2026-151684
CVE-2026-99473
·
Publicado
2026-11-19
·
Atualizado
2026-11-19
Descrição por
Pontuação
N/A
Não disponívelNão há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.
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.
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾