Anza has told Solana validators running its Agave client to patch a Linux kernel bug that can let attackers crash servers remotely. Anza's advisory thread on NoisyTCP, posted on 16 November 2026, calls for urgent action on every mainnet Agave node, staked or unstaked. Operators should install a patched kernel from their Linux distribution, or switch off a feature called SYN cookies until one ships. Neither step needs a validator restart.

NoisyTCP, tracked as CVE-2026-99288, is in the Linux kernel, the core of the operating system that handles network traffic. The fix therefore comes as a kernel update from each Linux distribution.

Anza's three steps for Agave validators facing NoisyTCP

Anza set out the fix in three steps for Agave operators:

  1. Upgrade to a patched kernel as soon as your distribution ships one, and check the distribution's security advisory to see whether the kernel you are running is affected.
  2. If no patched kernel is available yet, disable SYN cookies as a temporary measure. No validator restart is needed.
  3. Once the server has booted into a patched kernel, restore SYN cookies to their previous setting.

The exact commands and the checks that confirm they worked are in a post on the Solana Tech Discord, which Anza links from the thread. Operators should take the commands from there.

SYN cookies are a Linux defence against SYN floods, attacks that swamp a server with fake connection requests. Red Hat's advisory explains that turning them off blocks the code path where the crash happens, at the cost of weaker protection against those floods. That trade-off is why the setting goes back on after patching.

Red Hat's own mitigation sets the kernel parameter net.ipv4.tcp_syncookies to 0 and notes it applies per network namespace, so each container with its own network stack needs it separately.

How CVE-2026-99288 crashes a Linux server

CVE-2026-99288 is a timing bug in how the Linux kernel finds the connection an incoming TCP packet belongs to. According to the CVE record, memory for one connection can be recycled while another part of the kernel still holds its old address. The lookup can then return a half-built connection, and the kernel crashes when it reads an empty field.

Red Hat rates the bug Important, with a CVSS score of 7.5, and describes the result as a denial of service: an attacker sends traffic that triggers the race and the machine goes down. Neither the CVE record nor Red Hat describes it as a way to run code on the server. Red Hat's second mitigation, cutting the network card to a single receive queue, works because the race needs several queues processing packets at the same time.

The CVE record lists kernels from version 4.4 onward as affected, with fixes in 6.12.117, 6.18.63, 7.3.4 and 7.4-rc2. The record was published on 10 November 2026 and last updated on 16 November, the day of Anza's thread.

For Solana SOL$73.58+3.0%, the risk is downtime. A validator whose server crashes stops voting and producing blocks until it is back up, and stakers can compare validators' performance scores on our live validator list. We found no reports of NoisyTCP being used against Solana validators as of 17 November.

Which Linux distributions have shipped a NoisyTCP fix

Debian has patched kernels out for its current releases, while Ubuntu had not listed a fix for any release when we checked its tracker on 17 November 2026.

Distribution Status on 17 November 2026 Fixed kernel package
Debian 12 (bookworm) Fixed 6.1.192-2
Debian 13 (trixie) Fixed 6.12.117-1
Debian unstable (sid) Fixed 7.3.4-1
Ubuntu 16.04 to 26.10 Vulnerable, no fix listed None yet

The Debian figures come from the Debian security tracker. The Ubuntu CVE page marks its base linux package vulnerable on every release from 16.04 to 26.10, rates the bug Medium priority, and lists 14.04 as not affected. Ubuntu operators therefore fall under Anza's second step: with no patched kernel to install yet, the SYN cookie stopgap applies until Canonical ships one.

Firedancer operators and the Solana Foundation alert

Anza's thread names Agave nodes only. TokenPost reported that the Solana Foundation issued its own alert the same day, urging operators running Agave or Firedancer to patch and to disable SYN cookies until they can. We could not find the Foundation's original message.

The flaw sits in the kernel, below the validator client, so on our reading of the CVE any validator on an affected kernel is exposed whichever client it runs. Firedancer's developers had not published guidance on the bug that we could find.

NoisyTCP is separate from CVE-2026-98432, a different Linux TCP flaw rated 9.8 out of 10 that the Foundation warned validators about on 2 November, as Forklog reported. The Foundation's advice for that bug was different: restricting some packet processing and disabling Multipath TCP and connection migration.

What Solana validator operators should check next

This is Anza's second urgent operator notice this month, after it told validators to move to Agave 4.4.1 before epoch 1079. The next thing to watch is a patched kernel from each distribution, Ubuntu's above all. After rebooting into it, operators put SYN cookies back to their previous setting.

Anza's instructions are addressed to operators. Delegators who want to check their validator's record can start with uptime, one of the checks in our guide to choosing a Solana validator.

Keep up to date with the Solana eco
Follow us on Google News