Back to all lessons
Awareness Lessons
13 hours ago

Incomplete Kernel Patch Leaves KVM Guests Able to Read Host Memory on AMD Systems

Written by AI from the linked story. Not reviewed by an editor. How this works

An incomplete fix for a 2022 Linux KVM vulnerability left a dangling pointer that attackers with root access inside a guest VM could exploit to forge memory table entries and read up to 127 GB of host memory on AMD processors with nested virtualization enabled. This is a classic case of a partial patch introducing a residual risk that persists for years before being discovered and fully remediated. In multi-tenant cloud environments, the blast radius is especially severe because one compromised or malicious tenant could access memory belonging to other customers. The incident underscores that patch quality and regression testing are as important as patch speed, and that hypervisor-level vulnerabilities demand priority treatment given the privileged boundary they protect.

Tactical Insight

Immediate actions

  • Apply the fixed kernel shipped upstream on November 18, 2026 to all KVM hosts running AMD processors as soon as possible.
  • Disable nested virtualization on AMD KVM hosts as a temporary mitigation if immediate kernel patching is not feasible.
  • Audit all multi-tenant KVM deployments to confirm patch status and exposure before resuming normal operations.

Long-term improvements

  • Establish a formal patch validation process that includes regression testing for previously fixed CVEs when related code areas are modified.
  • Maintain a real-time inventory of hypervisor versions and enabled features (such as nested virtualization) across all host infrastructure.
  • Apply the principle of least privilege so that guest VM workloads never run with unnecessary root or elevated access inside the VM.

Detection measures

  • Subscribe to Linux kernel security mailing lists and CVE feeds specifically covering KVM and hypervisor components for early warning.
  • Implement memory integrity monitoring and anomaly detection at the hypervisor layer to flag unexpected cross-VM memory access patterns.
  • Track and alert on any changes to virtualization feature flags (e.g., nested virtualization toggles) in cloud infrastructure configuration management tools.

Back this up with a control

All controls and vendors

Training helps people spot this. These controls make the attack fail even on the day someone does not.