CycleOS 2026.10.15.1 is now available, and it brings two foundational upgrades: Linux kernel 6.18.57 and NVIDIA driver 580.167.08. It also includes the fix for CVE-2026-99999 (PwnEscape), a critical Linux kernel vulnerability.
The kernel and the GPU driver sit underneath everything you run on Cycle, so we don't touch them lightly. This release moves both forward by a full generation. Below, we walk through what changed in each and how it affects your workloads.
What's in CycleOS 2026.10.15.1
Here's the quick before-and-after for this release.
Component | Previous CycleOS | CycleOS 2026.10.15.1 |
|---|---|---|
Linux kernel | 6.12.112 | 6.18.57 |
NVIDIA driver | 570.158.01 | 580.167.08 |
Kernel branch | 6.12 LTS | 6.18 LTS |
NVIDIA driver branch | R570 | R580 |
Patched: CVE-2026-99999
Kernel 6.18.57 includes the fix for CVE-2026-99999, a critical Linux kernel vulnerability with a CVSS score of 9.3.
The bug lives in how the kernel's IPv4 stack handles checksum data. A specially crafted network packet could corrupt memory on the host, and researchers were able to use it to crash the host, leak data and even run code. The main attack path runs through virtual machines, where a malicious VM sends crafted traffic out through its virtual network interface.
If you run virtual machines on Cycle, we recommend restarting your servers onto this release as soon as you can. As of October 15, 2026, there are no confirmed reports of it being exploited in the wild, but that's not something worth waiting on.
Kernel 6.12.112 to 6.18.57
The jump from 6.12 to 6.18 rolls up six upstream kernel releases worth of work into one CycleOS update. Both are long-term support kernels, so you get a newer base without giving up a long maintenance runway. Linux 6.18 was released on November 30, 2025 and became the LTS kernel for that year.
Here's where the upgrade matters most for infrastructure running on Cycle:
- Newer server hardware support. Current-gen Intel and AMD servers are better supported, so adding new hardware to a cluster goes smoother.
- Better virtualization. Virtual machines on Cycle run more reliably, especially large VMs, and pick up extra security features.
- Memory and performance work. Under-the-hood tweaks help memory handling and encryption run more efficiently.
- Storage improvements. Better built-in health checks and new caching options for storage.
- Security hardening. New safeguards give the platform a stronger security baseline.
NVIDIA 570.158.01 to 580.167.08
Moving from the R570 branch to R580 is the bigger deal for GPU workloads. Version 580.167.08 shipped on June 15, 2026, so it carries close to a year of fixes and refinements on top of the original R580 release.
The highlights:
- CUDA 13 support. You can now run CUDA 13 workloads on Cycle, and anything built on CUDA 12 keeps working.
- Better support for newer GPUs. Improved support for NVIDIA's latest Blackwell data center GPUs.
- Stability and security fixes. A mature release with months of bug and security fixes behind it.
One item worth knowing before you roll it out:
- Older GPU generations. NVIDIA confirmed that R580 is the last Linux driver branch to support Maxwell, Pascal, and Volta GPUs. Those cards still work on this release, but it's a good time to start planning ahead if any are still in your fleet.
Getting the update
CycleOS never gets installed to disk. Instead, servers pull the latest OS over the network via iPXE each time they boot, so picking up the update only takes a restart.
A few tips for a smooth rollout:
- Start with a non-production cluster. Restart a staging or dev server first and let your workloads run on it for a bit.
- Check your GPU tooling. Confirm that your CUDA images are compatible with the R580 driver.
- Restart in waves. Restart production servers in batches so your services stay available the whole way through.
If anything looks off along the way, reach out to the Cycle team. We're always happy to help.
Frequently asked questions
Does CycleOS 2026.10.15.1 support CUDA 13?
Yes. CUDA 13 requires an R580-series driver, which this release includes. Workloads built on CUDA 12.x continue to run as well.
Do I need to install NVIDIA drivers inside my containers?
No. CycleOS delivers the driver to the host when a GPU server boots, then mounts the NVIDIA libraries into the containers that need them when they start. Your images just need your application and its dependencies.
Are older NVIDIA GPUs still supported?
Yes, for now. The R580 branch still supports Maxwell, Pascal and Volta GPUs, but NVIDIA has said it's the last Linux branch that will.