Skip to content

[Hotfix] v1.402.1 #7457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nmelehan-akamai merged 1 commit into from
May 7, 2026
+2 −1
Merged

[Hotfix] v1.402.1 #7457

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/guides/security/security-patches/cve-2026-31431-copy-fail-mitigation/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,8 +80,9 @@ For virtual machines (Linode VMs) you can:
* Older versions of the different Linux distributions remain available for customers to launch. The reason for this is that we cannot assess for our customers what risks they are willing to accept, and that we cannot break automated deployment pipelines for them. We strongly recommend that customers who continue to deploy older releases manually mitigate the vulnerability as described above.
* If you are using "GRUB 2" (default since August 2018), your Linode will boot with the kernel in the OS disk image. However, if you are [still using one of our kernels to boot](https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance), the latest kernel configuration (version 7.0.3) contains the patch for the vulnerability. Older Linode provided kernel configurations (e.g., "6.15.7-x86_64-linode169") remain vulnerable. Customers using these configurations are strongly encouraged to switch to the latest kernel and reboot, or use "GRUB 2" to boot from their own kernel on their primary disk, which has been Linode's default boot option since 2018.

For Linode Kubernetes Engine (LKE and LKE-E), the underlying nodes run a Linux kernel based on the Debian 12 (for LKE) and Ubuntu 22/24 (for LKE-Enterprise) distribution. Existing deployments will need patching until we can provide updated images. We will update this post when they are available. You can choose one of the following options:
For Linode Kubernetes Engine (LKE and LKE-E), the underlying nodes run a Linux kernel based on the Debian 12 (for LKE) and Ubuntu 22/24 (for LKE-Enterprise) distribution. These have been updated, but existing deployments will need patching. You can choose one of the following options:

* Upgrade to the latest images by [recycling your node pools](https://techdocs.akamai.com/linode-api/reference/post-lke-cluster-pool-recycle).
* The most durable option is to apply the mitigations outlined above via a DaemonSet. This will ensure mitigations are in place should scaling provision new nodes.
* Note: A `RuntimeDefault` seccomp profile is insufficient.
* Alternatively, mitigations can be applied manually or via infrastructure as code (IaC) tools like Terraform or Ansible.
Loading