CVE Catalog

CVE-2026-89923

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, KVM for s390 has a memory leak on vCPU destruction. Guest debug data (hw_bp_info, hw_wp_info, and old_data buffers) is not freed when a vCPU is destroyed, leading to unbounded memory leaks over VM lifetimes.

Risk Assessment

Long-running many virtual machines can lead to significant memory leaks, burdening the system and potentially causing performance issues.

Recommendation

Install a kernel patch that clears debug data on vCPU destruction.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Free guest debug data on vcpu destroy kvm_s390_clear_bp_data() is only called from kvm_arch_vcpu_ioctl_set_guest_debug(), i.e. when user space changes or disables debugging. A vCPU that is destroyed while hardware breakpoints are still armed - the normal case when the VMM just exits or crashes - leaks hw_bp_info, hw_wp_info and all old_data buffers, since generic KVM frees the vCPU right after kvm_arch_vcpu_destroy(). That is bounded by MAX_BP_COUNT entries, so roughly 8 KiB per vCPU, but it is unbounded over VM lifetimes. The allocations are GFP_KERNEL_ACCOUNT, so the charge also outlives the exiting process and pins dying memcgs. Fix by clearing the debug data on vCPU destruction. Calling it unconditionally is fine: struct kvm_vcpu is zero allocated, so for a vCPU that never enabled debugging the counters are 0 and the pointers NULL.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS