# CycleOS 2026.11.12.1: Linux Kernel 6.18.63 | Cycle.io

Canonical URL: https://cycle.io/blog/cycleos-2026-11-12-1

## CycleOS 2026.11.12.1: Linux Kernel 6.18.63

CycleOS 2026.11.12.1 moves to Linux kernel 6.18.63. It adds six stable point releases of fixes for virtualization, storage, networking and memory handling.

![cycle gear dark](https://cycle.io/_cdn/cycle%20gear%20dark-1592x1600-webp.webp?v=mw0xtywl)The Cycle Team

Published On Nov 12 20262 Min Read

![Cycle icon](https://cycle.io/_cdn/company.svg?v=mv8b8pno)

CycleOS 2026.11.12.1 is now available. It moves the Linux kernel from 6.18.57 to 6.18.63, and the NVIDIA driver stays on 580.167.08.

Last month's release did the heavy lifting by moving CycleOS onto the 6.18 LTS branch. This release is about keeping that foundation in good shape. Point releases don't get the same attention as a branch jump, but the kernel sits under every container and virtual machine you run on Cycle, so we treat them with the same care. Below, we cover what changed and what it means for your servers.

### What's in CycleOS 2026.11.12.1

Here's the quick before-and-after for this release.

| Component | Previous CycleOS | CycleOS 2026.11.12.1 |
| --- | --- | --- |
| Linux kernel | 6.18.57 | 6.18.63 |
| NVIDIA driver | 580.167.08 | 580.167.08 (unchanged) |
| Kernel branch | 6.18 LTS | 6.18 LTS |
| NVIDIA driver branch | R580 | R580 |

### Kernel 6.18.57 to 6.18.63

Releases within the 6.18.x line are maintenance updates on the long-term support branch. They carry bug and security fixes backported from upstream, not new features. Linux 6.18.63 shipped on November 10, 2026, and going from .57 to .63 pulls six of those releases into a single CycleOS update.

The full changelog is long. A lot of it covers hardware a CycleOS server will never touch, like laptop audio codecs and camera sensors. There's a few areas that do matter for infrastructure, though. Looking only at the [6.18.63 changelog](https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.63), here's what stood out:

-   **Virtualization.** Reliability fixes for how the kernel runs virtual machines and reports when one fails to start.
-   **Storage.** Reliability fixes for software RAID, the ext4 filesystem, write caching and NVMe drives, including NVMe storage over the network.
-   **Networking.** Fixes for IPv6 addresses when interfaces go down, bonded network interfaces and connection tracking.
-   **Memory.** More accurate memory tracking, plus a fix for stopping every process in a group at once.
-   Device isolation**.** Fixes for the AMD and Intel hardware that controls how devices like GPUs and network cards reach system memory.

### Getting the update

CycleOS is never installed to disk. Servers pull the latest OS over the network via iPXE each time they boot, so picking up this release only takes a restart.

A few tips for a smooth rollout:

1.  **Start with a non-production cluster.** Restart a staging or dev server first and let your workloads run on it for a bit.
2.  **Watch your heavier workloads.** If you run virtual machines or storage-heavy services, give them a little extra attention on that first server.
3.  **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](https://cycle.io/contact). We're always happy to help.

### Frequently asked questions

#### Do I need to change my containers or VMs?

No. Stable kernel updates fix bugs without changing how existing software behaves, so your images and VM configs stay as they are.

#### Does this affect CUDA workloads?

No. The NVIDIA driver stays on 580.167.08, so CUDA 13 and CUDA 12 workloads run the same as before.

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
