0x3521b0d13521…3521b0ce
Solana Foundation Orders All Node Operators to Act on NoisyTCP Kernel Flaw
Solana Foundation urged all Agave and Firedancer node operators to act immediately on NoisyTCP, CVE-2026-99288, covering staked and unstaked systems with no exceptions.

Outputs
Solana Foundation urged all Agave and Firedancer node operators to respond immediately to NoisyTCP, CVE-2026-99288.
The warning covers both staked and unstaked nodes with no staking-status exception.
If a patched kernel is available, operators should upgrade as soon as possible; if not, they should temporarily disable SYN Cookies.
Disabling SYN Cookies does not require restarting a validator, and the setting should be restored after starting a patched kernel.
Operators must check their Linux distribution's security notices to determine whether their installed kernel is affected.
The Solana Foundation has urged operators of every Agave and Firedancer node to respond immediately to NoisyTCP, a Linux kernel vulnerability tracked as CVE-2026-99288. The warning applies to both staked and unstaked nodes, leaving no operator outside its scope.
The Foundation issued the notice as a direct operational instruction rather than an advisory. It names the two major Solana validator clients — Agave, the successor to the Anza-maintained Rust client, and Firedancer, the client developed by Jump Crypto — and frames kernel remediation as an urgent task for anyone running either piece of software.
What should operators do first?
The guidance sets out a two-path response that depends entirely on patch availability. Operators should first check the security notices published by their Linux distribution to determine whether the kernel currently installed on a node is affected by CVE-2026-99288.
If the installed kernel is affected and a fix has already been released, operators should upgrade to the patched kernel as soon as possible. That path — applying the distribution's kernel update — is the Foundation's preferred remedy wherever it exists.
What if no patch is available yet?
Where a kernel patch has not yet shipped, the Foundation calls for a temporary configuration change: disabling SYN Cookies on the affected node. The notice states explicitly that this step does not require restarting a validator, meaning operators can apply it without interrupting block production or their participation in consensus.
The measure is explicitly temporary. Once a patched kernel has been installed and started, operators should return SYN Cookies to their previous setting, restoring the host's default defense against SYN flood attacks.
Why does staking status not matter?
The Foundation's notice includes both Agave and Firedancer operators with no exception based on staking status. That breadth matters for Solana's operational surface: unstaked nodes, including RPC endpoints and relay infrastructure, handle network traffic even though they do not vote in consensus. A kernel-level networking flaw on any of those machines can affect network reliability, not just validator uptime.
NoisyTCP sits in the Linux kernel rather than in Solana's own code, which is why the remediation runs through distribution security channels instead of a client software release. The Foundation directs operators to consult their distribution's security notices before choosing between the two remediation paths, since kernel versions and patch timing vary across distributions.
What happens next?
Operators on unpatched kernels now carry a defined interim obligation: disable SYN Cookies, verify kernel status against distribution advisories, and re-enable the setting once a patched kernel is running. The effective deadline for the permanent fix is set by each Linux distribution's release of a kernel update addressing CVE-2026-99288, and operators should monitor those advisories until their hosts run patched kernels with SYN Cookies restored.
via tokenpost.com (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
1,374 articles