PENTESTY · EDITORIAL ANALYSIS · · 4 min read
KVM on ARM64: who confirms the boundary between guest and host?
A guest kernel does not describe the hostâs condition. Review needs to identify who operates virtualization and which features are enabled.
By Pentesty
The published condition has a defined scope
In a September 2026 disclosure, Hyunwoo Kim described CVE-2026-89775 as a guest-to-host escape in KVM/ARM64 with nested virtualization enabled. The researcher reported a mainline kernel fix. The Ubuntu record, checked October 16, distinguishes packages and releases. These sources do not establish exposure of every Linux VM or compromise of a particular provider.
Inventory should start outside the guest
Imagine a testing service allowing customers to create virtual environments. Application owners know the image used for jobs, while another team operates the hosts. An update inside the VM may address a guest requirement while leaving the component enforcing isolation outside the acceptance decision.
Record architecture, distribution, kernel package, running instance and host owner. Add whether nested virtualization is available for that service and how the information was obtained. Processor capability, a feature offered by the product and a feature actually enabled require their own evidence.
Accountability needs to reach the right layer
Where the company operates the host, associate each answer with an asset and date. Where a provider operates that layer, request the covered product and service, applied guidance and limitations of the supplied evidence. A statement covering another instance family does not close the assessment.
Our BTR and code-execution analysis helps locate boundaries but addresses a different mechanism. Here the issue is a host virtualization condition. An application permission test cannot establish that isolation between machines withstands this vulnerability.
Define evidence without reproducing an escape
Agree a window and representative environment with platform operators. This proposal checks inventory, deployment and operation; a conclusion about resistance to the escape would need its own method and authorization. Retain that limitation in both the report and closure decision.
- Condition: identify the host and service, relevant configuration and confirmation source without inferring host state from the guest operating system.
- Change: connect distribution-specific guidance to completed maintenance and confirm the kernel actually running after the procedure.
- Continuity: run a legitimate test workload, observe VM creation and termination, and record errors, outcomes and acceptance owners.
- Outstanding work: where confirmation depends on a third party, retain the question, response, deadline and rationale for any operational exception.
A corrected image needs to become observed state
A catalog may offer a corrected image while older machines remain in service. Check existing hosts and the process creating future ones using the productâs supported maintenance approach. Our running-library review applies the same discipline of separating an available package from a loaded component.
Reopen the decision when instance family, kernel, user-facing capability or supplier changes. A useful conclusion identifies assessed assets, the evidence supporting their condition and areas outside observed scope. The result belongs to the examined combination, with a clear date and accountable owner.
Frequently asked questions
Is every Linux VM affected?
The disclosure concerns KVM/ARM64 with nested virtualization enabled. Match those conditions to the deployment and consult its vendor package status rather than generalizing from the Linux name.
Does updating the guest resolve a host condition?
Guest and host are different layers. Identify who operates the affected layer and which maintenance or confirmation applies to it.
Does an application test establish VM isolation?
It demonstrates only the application controls exercised. Assessing the isolation mechanism needs a specific hypothesis, environment, authorization and evidence.
What information should a provider supply?
Covered service and instance families, relevant condition, applied guidance, date and confirmation limits. Record points depending on a later response as well.
Sources and references
Original Pentesty analysis, published October 16, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.