feat(blog): add CVE-2026-53359 (Januscape) security advisory - #603
Conversation
Signed-off-by: Timur Tukaev <timur.tukaev@aenix.io> Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Timur Tukaev <timur.tukaev@aenix.io> Co-Authored-By: Claude <noreply@anthropic.com>
❌ Deploy Preview for cozystack failed.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a new blog post documenting security advisory CVE-2026-53359 ("Januscape"), a KVM/x86 shadow MMU use-after-free affecting Talos kernels, including impact description, mitigation via disabling nested virtualization on Talos and generic Linux hosts, automation notes, and post-fix guidance. ChangesSecurity Advisory Blog Post
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: ✨ Finishing Touches🧪 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 |
There was a problem hiding this comment.
Code Review
This pull request adds a security advisory blog post for CVE-2026-53359 ("Januscape"), a KVM guest-to-host escape vulnerability affecting Talos kernels, detailing mitigation steps by disabling nested virtualization. The review feedback suggests critical clarifications regarding Talos boot configuration: specifically, that extraKernelArgs is ignored on UEFI/UKI systems using systemd-boot (even on Talos >= 1.12) and requires baking the arguments into the boot image. Additionally, it recommends noting that all running VMs must be stopped before reloading the kvm module on generic Linux hosts.
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.
| # Talos >= 1.12 only: pin grubUseUKICmdline false so the args are applied | ||
| # (otherwise they are silently ignored on UEFI/UKI systems). | ||
| grubUseUKICmdline: false |
There was a problem hiding this comment.
On UEFI/UKI systems using systemd-boot (the default for UEFI installations since Talos 1.10), extraKernelArgs is always ignored because the kernel command line is embedded directly in the Unified Kernel Image (UKI). The grubUseUKICmdline option is specific to the GRUB bootloader (used for legacy BIOS or upgraded systems) and has no effect on systemd-boot systems.\n\nSetting grubUseUKICmdline: false will not make extraKernelArgs work on default UEFI/UKI systems. For those systems, the kernel arguments must be baked into the boot image via the Image Factory or imager. We should clarify this to prevent a false sense of security.
| # Talos >= 1.12 only: pin grubUseUKICmdline false so the args are applied | |
| # (otherwise they are silently ignored on UEFI/UKI systems). | |
| grubUseUKICmdline: false | |
| # For GRUB-based systems on Talos >= 1.12: pin grubUseUKICmdline false so the args are applied.\n # Note: This has no effect on systemd-boot UEFI/UKI systems, where extraKernelArgs is always ignored.\n grubUseUKICmdline: false |
| - kvm_amd.nested=0 | ||
| ``` | ||
|
|
||
| Both lines are safe on Intel and AMD — the one that does not match your CPU is ignored. On Talos **older than 1.12** the `grubUseUKICmdline` field does not exist and `extraKernelArgs` is ignored on UEFI/UKI nodes; there the args must be baked into the boot image via Image Factory. |
There was a problem hiding this comment.
Clarify that even on Talos >= 1.12, UEFI/UKI nodes using systemd-boot still ignore extraKernelArgs and require the arguments to be baked into the boot image.
| Both lines are safe on Intel and AMD — the one that does not match your CPU is ignored. On Talos **older than 1.12** the `grubUseUKICmdline` field does not exist and `extraKernelArgs` is ignored on UEFI/UKI nodes; there the args must be baked into the boot image via Image Factory. | |
| Both lines are safe on Intel and AMD — the one that does not match your CPU is ignored. On UEFI/UKI nodes using systemd-boot (the default for UEFI since Talos 1.10, regardless of the Talos version), extraKernelArgs is always ignored and the arguments must be baked into the boot image via Image Factory or imager. The grubUseUKICmdline field only applies to GRUB-based installations (legacy BIOS or upgraded nodes) on Talos >= 1.12. |
| options kvm_amd nested=0 | ||
| ``` | ||
|
|
||
| Then reboot the node (or reload the `kvm` module) for it to take effect. |
There was a problem hiding this comment.
Reloading the kvm module will fail with a "module is in use" error if any virtual machines are currently running on the host. It is helpful to remind operators to stop all running VMs before attempting to reload the module.
| Then reboot the node (or reload the `kvm` module) for it to take effect. | |
| Then reboot the node (or stop all running VMs and reload the kvm module) for it to take effect. |
Summary
Publishes a security advisory blog post for CVE-2026-53359 ("Januscape"), a KVM guest-to-host escape that affects all current Talos kernels.
What
content/en/blog/2026-07-07-security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/withindex.mdand a banner image.machine.installkernel args (and the generic-Linux equivalent).cozystack/ccp#17) and thecozystack:talos-bootstrap/cozystack:cluster-upgradeskills.Why
An exploit is public and no fixed Talos image has shipped yet, so operators need the mitigation now. Publishing it on the blog gives the community an authoritative, linkable reference.
Preview
cve-2026-53359-banner.png(1200×627)Summary by CodeRabbit