---
title: "Well, That Wasn't Fun: October 16 '26"
description: "Fly.io responded to CVE-2026-99999, a Linux kernel bug in IPv4 checksum-offload metadata validation, by patching and rebooting its entire fleet over 10 hours on October 16, 2026. The bug allowed a guest to rewrite two bytes of an IPv4 header after the host applied routing and firewall rules, enabling firewall bypass and an out-of-bounds read of up to 32 bytes of host memory. The team split each region into waves so no Managed Postgres cluster had both nodes rebooted simultaneously, with the largest region requiring 17 waves. Some hosts failed to return cleanly, including a chassis in gru that lost its power supply, delaying recovery for those machines until October 20. The post-mortem led to a new Incident Communications Plan that shifts communication decisions from incident responders to the exec team."
---

# Well, That Wasn't Fun: October 16 '26

[Fly.io](https://yomu.fyi/company/fly-io) · Nov 6, 2026

**Type:** Incident / postmortem

## Summary

Fly.io responded to CVE-2026-99999, a Linux kernel bug in IPv4 checksum-offload metadata validation, by patching and rebooting its entire fleet over 10 hours on October 16, 2026. The bug allowed a guest to rewrite two bytes of an IPv4 header after the host applied routing and firewall rules, enabling firewall bypass and an out-of-bounds read of up to 32 bytes of host memory. The team split each region into waves so no Managed Postgres cluster had both nodes rebooted simultaneously, with the largest region requiring 17 waves. Some hosts failed to return cleanly, including a chassis in gru that lost its power supply, delaying recovery for those machines until October 20. The post-mortem led to a new Incident Communications Plan that shifts communication decisions from incident responders to the exec team.

## Context

CVE-2026-99999 is a Linux kernel bug in IPv4 checksum-offload metadata validation that lets a guest rewrite two bytes of an IPv4 header after the host has already applied routing and firewall rules, enabling firewall bypass and an out-of-bounds read of up to 32 bytes of host memory.

## Approach / What changed

Patched the Linux kernel and rebooted the entire fleet host by host over 10 hours, splitting each region into waves so that no Managed Postgres cluster had both nodes in the same wave.

## Takeaways

- CVE-2026-99999 exploits a flaw in Linux IPv4 checksum-offload metadata validation, letting a guest rewrite two bytes of an IPv4 header after the host has already applied routing and firewall rules.
- The bug enables two attacks: a firewall bypass (rewriting source or destination IP) and an out-of-bounds read (rewriting header length to capture up to 32 bytes of adjacent host memory).
- Encrypt traffic between your own services even on a private network, scope agent credentials to the job with short expiration, and treat everything an agent reads as hostile.

## FAQ

### How does CVE-2026-99999 work?

The bug lets a guest rewrite two bytes of an IPv4 header after the host has already applied routing and firewall rules. This enables a firewall bypass (rewriting source or destination IP) and an out-of-bounds read (rewriting the header length to capture up to 32 bytes of adjacent host memory).

### What conditions are needed to exploit the bug?

The host must calculate the checksum in software for the exploit to succeed. The attacker must point the checksum at a different header field, pick a message that produces the desired checksum, and force software checksum calculation.

### Why was the initial status page vague?

The team posted an emergency maintenance notice without naming the CVE to avoid confirming vulnerability while the exploit was live. The post-mortem led to a new Incident Communications Plan that puts communication decisions on the exec team instead of the incident responders.

**Tags:** [CVE](https://yomu.fyi/topic/cve), [Fly.io](https://yomu.fyi/topic/fly-io), [Incident Response](https://yomu.fyi/topic/incident-response), [Linux](https://yomu.fyi/topic/linux), [Security](https://yomu.fyi/topic/security)

- Source: [Fly.io](https://fly.io/blog/well-that-wasnt-fun)
- Source URL: https://fly.io/blog/well-that-wasnt-fun
- Ingested by Yomu: 2026-11-06T12:01:16.574Z

[Read original post](https://fly.io/blog/well-that-wasnt-fun)
