Skip to content

Commit 0557399

Browse files
committed
docs: state CVE-2026-53359 exposure where the Talos line has no kernel fix
Talos v1.13.6 is the first release carrying both kernel fixes. These docs versions install from the 1.10, 1.11 or 1.12 lines, whose newest releases ship Linux 6.12.63, 6.12.62 and 6.18.35, while the fixes landed in 6.12.95 and 6.18.38. Say so, and name the only complete answer: move to a release that installs from the 1.13 line, then pin the image tag at v1.13.6 or newer. The pre-1.13 pages hardcode a 1.10 image tag while the release itself installs from a later line, so their note names no single line. For readers who cannot upgrade, disabling KVM nested virtualization is still the one available mitigation, so keep it, with both of the ways it silently does nothing. machine.install.extraKernelArgs reaches the kernel command line only on GRUB-booted nodes, and there only when machine.install.grubUseUKICmdline is false -- talosctl gen config writes it as true for Talos 1.12 and newer, so GRUB takes the command line from the UKI as well. On systemd-boot, which a fresh UEFI install of Talos 1.10 or newer uses, the command line lives inside the UKI and no machine-config setting reaches it at all. Signed-off-by: Aleksei Sviridkin <[email protected]>
1 parent 2e6346f commit 0557399

10 files changed

Lines changed: 60 additions & 0 deletions

File tree

‎content/en/docs/v0/install/kubernetes/talos-bootstrap.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,12 @@ talos-bootstrap --help
106106
- 10.96.0.0/16
107107
```
108108

109+
{{% alert title="No Talos release before v1.13.6 fixes CVE-2026-53359" color="warning" %}}
110+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and Talos v1.13.6 is the first release that carries them: every release of the 1.10, 1.11 and 1.12 lines is missing at least one, whichever of them this Cozystack version installs. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
111+
112+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
113+
{{% /alert %}}
114+
109115
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
110116

111117
```yaml

‎content/en/docs/v0/install/kubernetes/talosctl.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,12 @@ Discovered open port 50000/tcp on 192.168.123.13
130130
- 10.96.0.0/16
131131
```
132132

133+
{{% alert title="No Talos release before v1.13.6 fixes CVE-2026-53359" color="warning" %}}
134+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and Talos v1.13.6 is the first release that carries them: every release of the 1.10, 1.11 and 1.12 lines is missing at least one, whichever of them this Cozystack version installs. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
135+
136+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
137+
{{% /alert %}}
138+
133139
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
134140

135141
Note that VIP address is used for `machine.network.interfaces[0].vip.ip`:

‎content/en/docs/v1.0/install/kubernetes/talos-bootstrap.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,12 @@ talos-bootstrap --help
102102
- 10.96.0.0/16
103103
```
104104

105+
{{% alert title="No Talos release before v1.13.6 fixes CVE-2026-53359" color="warning" %}}
106+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and Talos v1.13.6 is the first release that carries them: every release of the 1.10, 1.11 and 1.12 lines is missing at least one, whichever of them this Cozystack version installs. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
107+
108+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
109+
{{% /alert %}}
110+
105111
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
106112

107113
```yaml

‎content/en/docs/v1.0/install/kubernetes/talosctl.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,12 @@ Discovered open port 50000/tcp on 192.168.123.13
126126
- 10.96.0.0/16
127127
```
128128

129+
{{% alert title="No Talos release before v1.13.6 fixes CVE-2026-53359" color="warning" %}}
130+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and Talos v1.13.6 is the first release that carries them: every release of the 1.10, 1.11 and 1.12 lines is missing at least one, whichever of them this Cozystack version installs. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
131+
132+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
133+
{{% /alert %}}
134+
129135
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
130136

131137
Note that VIP address is used for `machine.network.interfaces[0].vip.ip`:

‎content/en/docs/v1.1/install/kubernetes/talos-bootstrap.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,12 @@ talos-bootstrap --help
102102
- 10.96.0.0/16
103103
```
104104

105+
{{% alert title="No Talos release before v1.13.6 fixes CVE-2026-53359" color="warning" %}}
106+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and Talos v1.13.6 is the first release that carries them: every release of the 1.10, 1.11 and 1.12 lines is missing at least one, whichever of them this Cozystack version installs. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
107+
108+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
109+
{{% /alert %}}
110+
105111
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
106112

107113
```yaml

‎content/en/docs/v1.1/install/kubernetes/talosctl.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,12 @@ Discovered open port 50000/tcp on 192.168.123.13
126126
- 10.96.0.0/16
127127
```
128128

129+
{{% alert title="No Talos release before v1.13.6 fixes CVE-2026-53359" color="warning" %}}
130+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and Talos v1.13.6 is the first release that carries them: every release of the 1.10, 1.11 and 1.12 lines is missing at least one, whichever of them this Cozystack version installs. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
131+
132+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
133+
{{% /alert %}}
134+
129135
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
130136

131137
Note that VIP address is used for `machine.network.interfaces[0].vip.ip`:

‎content/en/docs/v1.2/install/kubernetes/talos-bootstrap.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,12 @@ talos-bootstrap --help
102102
- 10.96.0.0/16
103103
```
104104

105+
{{% alert title="No Talos release before v1.13.6 fixes CVE-2026-53359" color="warning" %}}
106+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and Talos v1.13.6 is the first release that carries them: every release of the 1.10, 1.11 and 1.12 lines is missing at least one, whichever of them this Cozystack version installs. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
107+
108+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
109+
{{% /alert %}}
110+
105111
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
106112

107113
```yaml

‎content/en/docs/v1.2/install/kubernetes/talosctl.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,12 @@ Discovered open port 50000/tcp on 192.168.123.13
126126
- 10.96.0.0/16
127127
```
128128

129+
{{% alert title="No Talos release before v1.13.6 fixes CVE-2026-53359" color="warning" %}}
130+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and Talos v1.13.6 is the first release that carries them: every release of the 1.10, 1.11 and 1.12 lines is missing at least one, whichever of them this Cozystack version installs. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
131+
132+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
133+
{{% /alert %}}
134+
129135
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
130136

131137
Note that VIP address is used for `machine.network.interfaces[0].vip.ip`:

‎content/en/docs/v1.3/install/kubernetes/talos-bootstrap.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,12 @@ talos-bootstrap --help
102102
- 10.96.0.0/16
103103
```
104104

105+
{{% alert title="No Talos 1.12 release fixes CVE-2026-53359" color="warning" %}}
106+
[CVE-2026-53359](/blog/2026/07/security-advisory-cve-2026-53359-januscape-kvm-guest-to-host-escape/) ("Januscape") and CVE-2026-46113 are related use-after-free bugs in the KVM x86 shadow MMU that let a guest VM escape to its host. Both fixes live in the kernel, and no Talos 1.12 release carries the one for CVE-2026-53359: the newest, v1.12.9, ships Linux 6.18.35, while that fix landed in 6.18.38. The complete fix is Talos v1.13.6 or newer: upgrade to a Cozystack release that installs from the Talos 1.13 line, then set the Talos image tag to `v1.13.6` or newer.
107+
108+
If you cannot upgrade and you run untrusted guests, disabling KVM nested virtualization (`kvm_intel.nested=0`, `kvm_amd.nested=0`) removes the entry point the published exploit relies on. Treat it as a stop-gap rather than a fix, and note how easily it ends up doing nothing: `machine.install.extraKernelArgs` reaches the kernel command line only on GRUB-booted nodes, and there only when `machine.install.grubUseUKICmdline` is `false`. `talosctl gen config` writes that field as `true` for Talos 1.12 and newer, which makes GRUB take the command line from the Unified Kernel Image as well, so set it to `false` alongside the arguments. On Talos 1.10 and 1.11 the field does not exist and is not needed. None of this helps on systemd-boot: a fresh UEFI install of Talos 1.10 or newer boots through it, and the kernel command line lives inside the Unified Kernel Image, so config-side arguments are ignored whatever the machine config says. There the arguments have to be baked into the boot assets with [Image Factory or Imager](https://www.talos.dev/v1.12/talos-guides/install/boot-assets/).
109+
{{% /alert %}}
110+
105111
1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:
106112

107113
```yaml

0 commit comments

Comments
 (0)