The Linux kernel's KVM module did not prevent clearing the KVM_MEM_GUEST_MEMFD flag on an existing memslot that was originally created with this flag set. This improper handling led to a use-after-free vulnerability because KVM failed to unbind from the guest_memfd instance when the flag was cleared. The vulnerability was detected by KASAN (Kernel Address Sanitizer) showing slab-use-after-free in kvm_gmem_release. The fix involves rejecting attempts to disable KVM_MEM_GUEST_MEMFD on memslots initially created with guest_memfd binding, preventing the use-after-free condition. This patch addresses the underlying cause rather than just mitigating the symptom.

Successful exploitation of this vulnerability can lead to use-after-free memory corruption within the KVM kernel module. This may result in system instability, crashes, or potentially privilege escalation due to corrupted kernel memory. The CVSS 3.1 vector indicates local attack vector with low attack complexity, requiring low privileges, no user interaction, and impacts confidentiality, integrity, and availability with high severity.

A fix has been implemented in the Linux kernel to reject attempts to toggle the KVM_MEM_GUEST_MEMFD flag on existing memslots that were initially created with this flag. Users and administrators should apply the official Linux kernel updates that include this fix. Since this is a kernel-level vulnerability, upgrading to a patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; therefore, check the Linux kernel vendor advisory for the exact fixed versions and apply updates accordingly.