test(e2e): disable KVM nested virtualization (CVE-2026-53359) - #3234
test(e2e): disable KVM nested virtualization (CVE-2026-53359)#3234Andrei Kvapil (kvaps) wants to merge 2 commits into
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughUpdates the generated Talos patch YAML in the e2e cluster preparation script to disable UKI cmdline usage and add kernel arguments that turn off nested KVM on Intel and AMD. ChangesTalos Patch Kernel Args Update
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the E2E cluster preparation configuration to address a critical security vulnerability. By disabling nested virtualization at the kernel level, the changes prevent potential guest-to-host escapes while waiting for upstream kernel patches to be integrated into the Talos release cycle. Highlights
New Features🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the end-to-end cluster preparation configuration in hack/e2e-prepare-cluster.bats to disable KVM nested virtualization (kvm_intel.nested=0 and kvm_amd.nested=0) as a mitigation for CVE-2026-53359. There are no review comments, and I have no additional feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
IvanHunters
left a comment
There was a problem hiding this comment.
LGTM. The machine.install patch lands cluster-wide via --config-patch=@patch.yaml, and grubUseUKICmdline: false is correct and necessary for the pinned talosctl v1.13.5 (which defaults it true). No e2e regression.
d0e7563 to
40e0a6f
Compare
Set kvm_intel.nested=0 and kvm_amd.nested=0 in the e2e Talos machine-config patch to mitigate CVE-2026-53359 (Januscape), a KVM guest-to-host escape reachable only when nested virtualization is exposed to the guest. Both args are set so one config covers Intel and AMD hosts. Signed-off-by: Andrei Kvapil <andrei.kvapil@aenix.io> Assisted-By: Claude <noreply@anthropic.com>
…os >=1.12 (CVE-2026-53359) On Talos >1.11 the base defaults machine.install.grubUseUKICmdline=true (UKI cmdline), which Talos rejects together with extraKernelArgs and which ignores them anyway. Pin it false so the nested=0 args land on the Talos-built cmdline. Signed-off-by: Andrei Kvapil <andrei.kvapil@aenix.io> Assisted-By: Claude <noreply@anthropic.com>
40e0a6f to
c440a7c
Compare
|
Closing: superseded by #3240. The change here disables KVM nested virtualization on the sandbox nodes and pins |
What this PR does
Disables KVM nested virtualization in the E2E Talos machine-config patch to mitigate CVE-2026-53359 ("Januscape"), a guest-to-host escape in the Linux KVM/x86 shadow MMU (a use-after-free in
kvm_mmu_get_child_sp()caused by shadow-page role confusion).The vulnerable code path is only reachable when a guest is allowed to use nested virtualization (i.e. the guest is given the
vmx/svmCPU feature and runs its own nested guest). Settingkvm_intel.nested=0andkvm_amd.nested=0on the host removes the attack surface entirely, independent of the node kernel patch level.The bug was fixed upstream in commit
81ccda30b4e8and in stable kernels6.12.95/6.6.144/6.1.177/6.18.38/7.1.3(2026-07-04); as of this PR no released Talos ships a fixed kernel yet, so disabling nested virtualization is the reliable mitigation. Both args are set so a single config works on Intel and AMD hosts — the non-matching one is silently ignored.Part of a coordinated set of PRs (see Related PRs below).
Release note
Related PRs
Coordinated CVE-2026-53359 (Januscape) nested-virtualization mitigation across Cozystack repos:
cozystack/genericpresets (canonical source)Summary by CodeRabbit