CVE-2026-89928

8.8

Linux · Kernel

A use-after-free vulnerability in the Linux kernel KVM subsystem allows local users to potentially trigger memory corruption during lockless rmap walks.

Executive summary

A race condition in the Linux kernel KVM memory management subsystem could allow a local attacker to achieve privilege escalation or system instability via a use-after-free exploit.

Vulnerability

The vulnerability exists in the KVM x86 memory management unit, where a lockless rmap walk incorrectly re-reads the rmap value instead of consuming the locked value. This race condition allows a local attacker with low privileges to trigger a use-after-free scenario when a writer thread frees memory while a walker is processing it.

Business impact

The exploitation of this flaw can lead to a complete compromise of the host system, including unauthorized access to memory, privilege escalation, or unexpected service termination. Given the CVSS score of 8.8, this represents a high-severity risk to virtualized environments, as it allows a guest or local user to potentially escape into the host kernel or destabilize the hypervisor.

Remediation

Immediate Action: Update the Linux kernel to version 6.18.51, 7.2.5, or later, as provided by your distribution vendor.

Proactive Monitoring: Monitor system logs for kernel panic events or memory-related segmentation faults that may indicate an exploitation attempt.

Compensating Controls: Restrict local user access to the system and ensure that KVM guests are appropriately sandboxed or isolated from sensitive host resources while the patch is being staged.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

This vulnerability presents a significant risk to the integrity and availability of Linux-based hypervisors. Administrators should prioritize the application of the latest kernel security updates across all affected infrastructure to mitigate the risk of local privilege escalation and potential system crashes.

More Linux CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources