You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8a84587
Browse filesBrowse the repository at this point in the historyBrowse files
blog: retract the CVE-2026-53359 nested-virtualization mitigation
Talos v1.13.6 shipped on 2026-07-09 with Linux 6.18.38, the first kernel
carrying the fixes for both CVE-2026-53359 and its sibling CVE-2026-46113. The
advisory was written while no fixed Talos release existed, so it recommended
disabling KVM nested virtualization and stated that Cozystack VMs do not need
the feature. Both claims are now wrong: the bug is fixed in the kernel, and
taking nested virtualization away from workloads that rely on it buys nothing.
Lead with an update note, so a reader who acted on the first version learns the
recommendation changed rather than finding a silently rewritten page. Say which
Talos lines carry the fix and which never will, recommend the upgrade, and keep
disabling nested virtualization only as a stop-gap for clusters that cannot
upgrade yet. Non-Talos hosts get a fix path too -- their distribution's kernel
update -- named without a version, because which stable series carry both
patches has not been established here and a security advisory is no place to
guess.
Correct the stop-gap's caveats, which conflated two unlike failures. Omitting
grubUseUKICmdline: false on Talos 1.12 and newer does not quietly drop the
kernel arguments -- Talos rejects the config outright, and says so. The quiet
failure is systemd-boot, where the command line lives inside the UKI and the
arguments are accepted and then ignored with nothing reported; point the reader
at /proc/cmdline instead of at an assumption.
Drop the automation section: it advertised skills that prescribe and verify a
mitigation this advisory no longer recommends.
Signed-off-by: Aleksei Sviridkin <[email protected]>
description: "CVE-2026-53359 (\"Januscape\") is a KVM guest-to-host escape affecting all current Talos kernels. Cozystack clusters that run VMs or tenant Kubernetes should disable nested virtualization now."
6
+
description: "CVE-2026-53359 (\"Januscape\") is a KVM guest-to-host escape. It is fixed in the kernel: Talos v1.13.6 ships Linux 6.18.38, which carries the patches for this and the related CVE-2026-46113. Upgrade — nested virtualization stays available."
**Severity:** High for clusters running virtualization. **Status:** No fixed Talos release yet — mitigation required now.
18
+
**Update, 2026-07-09.** Talos v1.13.6 has shipped with the fixed kernel. This advisory originally recommended disabling KVM nested virtualization, because at the time no fixed Talos release existed. That recommendation is superseded: upgrade to Talos v1.13.6 or newer and keep nested virtualization enabled. Disabling it remains a stop-gap for clusters that cannot upgrade yet.
19
+
20
+
**Severity:** High for clusters running virtualization. **Status:** Fixed in Talos v1.13.6 (Linux 6.18.38), released 2026-07-09.
19
21
20
22
## What happened
21
23
22
24
On 2026-07-06 a Linux kernel vulnerability, **CVE-2026-53359** ("Januscape"), was publicly disclosed together with a working exploit. It is a use-after-free in the KVM/x86 shadow MMU that lets a **guest VM break out to its host** (the cluster node) or crash the node's kernel. It affects both Intel and AMD CPUs and has been latent in the kernel since 2010.
23
25
24
-
The upstream fix shipped in stable kernels (6.18.38, 6.12.95, 6.6.144, 6.1.177, 7.1.3) on 2026-07-04, but **Talos Linux has not yet released an image with the fixed kernel.** Every current Talos version still runs a vulnerable kernel.
26
+
The upstream fix shipped in stable kernels (6.18.38, 6.12.95, 6.6.144, 6.1.177, 7.1.3) on 2026-07-04. **Talos v1.13.6**, released on 2026-07-09, is the first Talos release to carry it.
27
+
28
+
CVE-2026-53359 has a sibling: **CVE-2026-46113**, the same class of use-after-free in the same code path, fixed by a separate upstream patch. A kernel is only fully fixed once it carries both — in the 6.18 series that means 6.18.38 or newer (CVE-2026-46113 landed in 6.18.30), in the 6.12 series 6.12.95 or newer (it landed in 6.12.88). No release on the Talos 1.10, 1.11 or 1.12 lines carries both: the newest of each ships Linux 6.12.63, 6.12.62 and 6.18.35 respectively, and there is no fixed release planned for those lines.
25
29
26
30
## Who is affected
27
31
@@ -36,9 +40,19 @@ The exploit needs two things a tenant already has: root inside their own VM, and
36
40
37
41
KubeVirt's sandboxing (unprivileged containers, seccomp, SELinux) does **not** stop this — the bug is in the host kernel and is reached through the normal KVM interface every VM must use.
Upgrade nodes to **Talos v1.13.6** or newer. The bug is fixed in the kernel, so nested virtualization stays enabled and workloads that rely on it keep working.
46
+
47
+
Only the 1.13 line has a fixed release. A cluster on Talos 1.10, 1.11 or 1.12 has to move to the 1.13 line to reach the fix; for Cozystack clusters that means upgrading to a release that installs from it.
40
48
41
-
Cozystack VMs do not need nested virtualization. Disabling it removes the attack surface entirely, regardless of kernel version.
49
+
Hosts that do not run Talos need a kernel carrying both patches — take your distribution's kernel update.
50
+
51
+
**Warning: upgrading reboots the node.** Roll it out **one node at a time**, waiting for each node to become `Ready` (and for etcd quorum to recover on control-plane nodes) before moving to the next.
52
+
53
+
## If you cannot upgrade yet: disable nested virtualization
54
+
55
+
The published exploit reaches the bug through nested virtualization exposed to the guest. Disabling it closes that entry point. This is a stop-gap, not a fix — the kernel bug is still there — and it takes the feature away from any workload that needs it.
42
56
43
57
### Talos (most clusters)
44
58
@@ -47,15 +61,20 @@ Add to your Talos machine config, under `machine.install`:
47
61
```yaml
48
62
machine:
49
63
install:
50
-
# Talos >= 1.12 only: pin grubUseUKICmdline false so the args are applied
51
-
# (otherwise they are silently ignored on UEFI/UKI systems).
64
+
# Talos >= 1.12 only: `talosctl gen config` writes this as true, and Talos
65
+
# refuses a config that carries both it and extraKernelArgs. The field does
66
+
# not exist before 1.12, and it has no effect on systemd-boot nodes.
52
67
grubUseUKICmdline: false
53
68
extraKernelArgs:
54
69
- kvm_intel.nested=0
55
70
- kvm_amd.nested=0
56
71
```
57
72
58
-
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.
73
+
Both lines are safe on Intel and AMD — the one that does not match your CPU is ignored.
74
+
75
+
Two caveats, and they fail differently. On Talos 1.12 and newer, omitting `grubUseUKICmdline: false` does not quietly drop the arguments — Talos rejects the whole config with `install.extraKernelArgs and install.grubUseUKICmdline can't be used together`. Before 1.12 the field does not exist and is not needed.
76
+
77
+
**The second caveat is the quiet one.** These arguments only take effect on GRUB-booted nodes. A fresh UEFI install of Talos 1.10 or newer boots through systemd-boot, where the kernel command line lives inside the Unified Kernel Image; there Talos accepts the arguments and then ignores them, reporting nothing, and `grubUseUKICmdline` does not help because there is no GRUB. Clusters upgraded into 1.10 keep their existing GRUB bootloader and are unaffected. On systemd-boot nodes the arguments have to be baked into the boot assets via Image Factory or Imager. After applying either way, confirm on the node with `cat /proc/cmdline` rather than assuming it took.
59
78
60
79
**Apply it in two steps — `talm apply`, then `talm upgrade`.** First push the updated machine config to the node, then re-run the Talos installer so the kernel arguments are written into the boot configuration (a plain `talm apply` alone does not rewrite the boot config). You can upgrade to the *same* Talos version you are already on — the point is to re-run the installer with the new arguments:
**Warning: this reboots the node.** Roll it out **one node at a time**, waiting for each node to become `Ready` (and for etcd quorum to recover on control-plane nodes) before moving to the next.
89
+
**Warning: `talm upgrade` reboots the node.** Roll it out one node at a time, as above.
Then reboot the node (or reload the `kvm` module) for it to take effect.
82
101
83
-
## Automation
84
-
85
-
We have updated our Cozystack Claude Code skills to prescribe and verify this mitigation during bootstrap and upgrades, so the setting is placed under `machine.install` and persists across future Talos upgrades: [cozystack/ccp#17](https://github.com/cozystack/ccp/pull/17).
86
-
87
-
You can use the `cozystack:talos-bootstrap` and `cozystack:cluster-upgrade` skills to apply and verify the change automatically.
88
-
89
-
## After a fixed Talos ships
90
-
91
-
Once Talos releases an image with the patched kernel (6.18.38 or newer), upgrade normally. You may keep nested virtualization disabled as a hardening measure, or re-enable it (remove the two arguments) if a specific workload requires it. We will notify you when a fixed Talos release is available.
0 commit comments