On 16 November 2026, Anza and the Solana Foundation told validators to patch CVE-2026-99288, a Linux kernel TCP flaw known as NoisyTCP that, under certain conditions, can crash a server remotely. As reported by Solana Compass and TokenPost, Anza's call covers every mainnet Agave node, staked or unstaked, and the Foundation's notice names Firedancer nodes too. Debian and Amazon Linux list fixes. When we read Ubuntu's security tracker on 21 November, it marked the linux kernel package Vulnerable on every Ubuntu release we saw listed (26.10 down to 16.04). Anza's workaround, per Solana Compass, is to disable SYN cookies until a patched kernel is installed, which needs no validator restart but weakens a defence against flood attacks. Solana Compass reported that it found no reports of NoisyTCP being used against Solana validators as of 17 November.

Key Takeaways

  • NoisyTCP is a race in the Linux kernel's TCP lookup that leads to a NULL pointer dereference and a crash. Solana Compass describes the effect as denial of service, and says neither the CVE record nor Red Hat describes code execution. Red Hat rates attack complexity High, and its own score vector lists high confidentiality and integrity impact as well.
  • Anza's reported steps (a Solana Compass paraphrase; we did not read the thread): install a patched kernel as soon as your distribution ships one, otherwise disable SYN cookies temporarily, then restore them after patching.
  • Debian (bookworm and trixie security builds) and Amazon Linux 2 and 2023 list fixes. Ubuntu's tracker marked its kernel package Vulnerable on 26.10, 26.04, 24.04, 22.04, 20.04, 18.04 and 16.04. We did not read Red Hat's per-release table or check other distributions.
  • Severity scores differ: 7.5 at Red Hat and Amazon, 5.9 shown on Ubuntu's page.
  • It is the second Linux TCP advisory to validators in about two weeks. Gossip data cannot tell us how much stake runs a vulnerable kernel.

What Anza and the Foundation Said

According to Solana Compass (17 November), Anza posted an advisory thread on 16 November telling operators of every mainnet Agave node, staked or unstaked, to act urgently. Solana Compass paraphrases the three steps: upgrade to a patched kernel as soon as the distribution ships one and check its security advisory, disable SYN cookies as a temporary measure if no patched kernel is available (no validator restart needed), and restore SYN cookies to their previous setting once the server has booted into a patched kernel. The exact commands are in a Solana Tech Discord post linked from the thread, which we did not read.

The Foundation issued its own alert. TokenPost (16 November) reports that it urges operators of mainnet validators running Agave or Firedancer to patch promptly, and that operators who cannot get the patch immediately should disable SYN cookies temporarily. PANews's headline says the vulnerability should be patched as soon as possible. Solana Compass notes that Anza's thread names Agave only, that it could not find the Foundation's original message, that it found no Firedancer developer guidance, and that on its reading any validator on an affected kernel is exposed whichever client it runs. The sources do not establish whether Anza's thread or the Foundation's notice came first on 16 November.

What the Flaw Is

The CVE's title is "inet: reject unhashed sockets during established lookups". According to the Debian, Ubuntu and Solana Compass pages, the Linux kernel's lockless lookup of an established TCP connection can return a socket that has been recycled and is no longer hashed. The kernel then dereferences an empty field and crashes. Solana Compass describes it as a race that needs several queues processing packets at once, and says 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 fix makes the lookup drop the socket reference and retry. Red Hat classifies it as CWE-476, a NULL pointer dereference.

Solana Compass says neither the CVE record nor Red Hat describes code execution, and describes the result as denial of service. Red Hat rates the attack complexity High. The CVE record was published on 10 November and updated on 16 November, and the Ubuntu and Amazon pages both show a publication date of 10 November. No page we read states who reported it.

Who Has a Fix Today

Whether an operator can simply update depends on the distribution. We read the security pages of Debian, Ubuntu, Red Hat and Amazon on 21 November.

DistributionStatus when we read it (21 November)Detail
Debian 12 (bookworm)Fixed in the security archive6.1.192-2 (DLA-4906-1)
Debian 13 (trixie)Fixed in the security archive6.12.117-1 (DSA-6628-1)
Debian forky and unstableFixed7.3.4-1 and 7.3.5-1
Amazon Linux 2Fixedkernel and kernel-5.4 released 17 November; kernel-5.10 and 5.15 released 12 November
Amazon Linux 2023Fixedkernel and kernel6.12 released 12 November; kernel6.18 released 17 November
Ubuntu 26.10, 26.04, 24.04, 22.04, 20.04, 18.04, 16.04Vulnerable (kernel package "linux")Priority High; the page shows a CVSS 3 score of 5.9; 14.04 is listed as not affected; the cloud kernels (aws, azure, gcp) are vulnerable on most releases; the page was truncated in our read and no fixed versions appeared in the text we saw
Red HatRated Important, CVSS 7.5, scores marked preliminaryWe did not read a per-release table, and did not check other distributions such as Rocky or Alma

The Scores Disagree

Red Hat rates the flaw Important with CVSS 3.1 of 7.5 and says its scores are "preliminary and subject to review". Amazon Linux also shows 7.5. The Red Hat page carries a second 7.5 under the cve.org column, with a different vector. Ubuntu's page shows a CVSS 3 score of 5.9 alongside its own priority of High, and does not clearly name who scored it. We could not read the NVD page, so there is no NVD score. The Red Hat and cve.org vectors also differ in impact: Red Hat's own vector scores confidentiality, integrity and availability all High, while the cve.org and Amazon vectors score availability only. We did not read Ubuntu's vector, so we cannot explain its 5.9.

A glass server rack tower with a stream of glowing data packets arriving from the left, one packet cracked, and a thin ring of light around the tower with a gap
A cracked data packet reaching a server tower with a partial ring of protection

The Workaround and What It Costs

Anza and the Foundation, as reported, put disabling SYN cookies ahead of waiting when no patched kernel exists. Red Hat's page lists the mitigation as setting net.ipv4.tcp_syncookies to 0, which applies per network namespace, or alternatively reducing the network interface to a single receive queue and disabling receive packet steering and receive flow steering. Red Hat warns that turning off SYN cookies weakens protection against SYN floods, and Anza's reported third step is to restore the setting after patching. Those commands are Red Hat's documentation, not Anza's, whose exact commands sit in a Discord post we did not read. We found no source that quantifies the trade-off.

The Second Linux Flaw in Two Weeks

This is not the first Linux TCP advisory to validators this month. Anza and the Foundation warned about CVE-2026-98432 on 1 and 2 November, as covered in the TokenPost report of 2 November, with a different set of mitigations and, per Solana Compass, a higher score.

ItemCVE-2026-98432 (early November)CVE-2026-99288, NoisyTCP (mid November)
Warned to validatorsAnza on 1 November, the Foundation on 2 NovemberAnza and the Foundation on 16 November
Severity cited (not like for like)9.8 (Solana Compass)7.5 at Red Hat and Amazon; 5.9 shown on Ubuntu's page
Reported effectNot examined here; the mitigations target Multipath TCP, connection migration and IPv4 IP options (TokenPost)Denial of service; neither the CVE record nor Red Hat describes code execution (Solana Compass)
Mitigation givenDisable Multipath TCP and connection migration, filter IPv4 packets with IP options (TokenPost)Disable SYN cookies temporarily, restore after patching (Anza, via Solana Compass)
Ubuntu status22.04 and 24.04 standard kernels vulnerable on 2 November (TokenPost); we did not check whether that has since changedKernel package marked Vulnerable on the releases listed above when we read it on 21 November
Exploitation against SolanaNone reported (TokenPost)None reported as of 17 November (Solana Compass)
Linux TCP advisories to validators, 1 to 20 November 2026Anza and the Solana Foundation warned validators about CVE-2026-98432 on 1 and 2 November. CVE-2026-99288, called NoisyTCP, was published on 10 November, and Amazon released a fix for Amazon Linux 2023 on 12 November. Anza and the Foundation issued their NoisyTCP guidance on 16 November, and the CVE record was updated the same day. Amazon released further fixes on 17 November, and Ubuntu's page was last updated on 20 November, when we read it on 21 November it marked its kernel package Vulnerable on the releases listed.LINUX TCP ADVISORIES TO VALIDATORS, 1 TO 20 NOVEMBER1 to 20 November 2026Anza or FoundationCVE record and vendors1-2 NovAnza and the Foundation warn on CVE-2026-9843210 NovCVE-2026-99288 published; Ubuntu and Amazon list it12 NovAmazon Linux 2023 kernel fix released16 NovAnza thread and Foundation notice on NoisyTCP16 NovCVE record updated (Amazon page modified)17 NovAmazon Linux releases more kernel fixes20 NovUbuntu tracker page last updated (we read it on 21 Nov)
Source: TokenPost (2 November), Solana Compass (17 November), Amazon Linux Security Center and Ubuntu Security (read 21 November 2026). The 16 November order of Anza's thread, the Foundation notice and the CVE update is not established by the sources.

What We Can and Cannot See

Solana's gossip network does not reveal an operating system or kernel version, so we cannot say how much stake runs an affected kernel. What we can say from Solana's public RPC on 20 November is the size of the network the notices could apply to: 3,764 nodes appear in gossip, and 685 vote accounts (662 current, 23 delinquent) hold about 429.0M SOL of activated stake. The gossip count includes RPC nodes, non-Agave clients and non-voting nodes, so it is an upper bound (our framing), not an exposure estimate.

Because the flaw is in the kernel, it is separate from the validator software versions we tracked in our Agave 4.4.1 report. A validator can be fully up to date on Agave or Firedancer and still run a vulnerable kernel. Our reading, not stated by any advisory: a provider running many validators on one kernel build could have many machines exposed together, and we have no data on any provider's kernels. The Solflare incident in our report on the Solflare validator incident was a key compromise and is unrelated to NoisyTCP.

What to Watch Next

  • Ubuntu's fixes. The tracker's status for each release, and for the cloud kernels, is the most direct measure of how many validators can patch by updating packages.
  • The Foundation's original notice. Solana Compass could not find it, and we did not read it either.
  • Any report of exploitation. As of 17 November, Solana Compass had found none.
  • Firedancer guidance. None had been found by Solana Compass.
  • Other validator work. Operators are also tracking the feature gate timing we describe in our direct mapping report.

Known Discrepancies

Coverage of NoisyTCP varies in tone and detail, and several claims go beyond the advisories.

Claim in circulationWhat the sources support
A critical vulnerabilityA KuCoin News headline calls it critical. Red Hat and Amazon rate it Important at CVSS 7.5, Ubuntu's page shows 5.9, and Solana Compass describes a denial of service.
It affects all Solana validatorsA KuCoin News headline says so. Anza's call covers every mainnet Agave node, staked or unstaked, and the Foundation notice names Firedancer. The flaw is in the Linux kernel, so exposure depends on the operating system, not the client.
Anza and the Foundation gave the same guidanceAnza's thread names Agave only and the Foundation names Agave and Firedancer, as reported. Solana Compass could not find the Foundation's original message.
The Foundation notice and Anza thread date from 16 NovemberTokenPost dates the Foundation notice 16 November (11:15 EST). Solana Compass, dated 17 November, says Anza posted on 16 November. The order is not established.
Patched kernels are availableDebian and Amazon Linux list fixes. Ubuntu's tracker marked its kernel package Vulnerable when we read it. We did not read Red Hat's per-release status.

Sources and Methodology

We read Solana Compass (17 November), TokenPost (16 November) and PANews (17 November) for the Anza and Foundation guidance, and the security pages of Ubuntu, Debian, Red Hat and Amazon Linux on 21 November. The Ubuntu page was truncated in our read, so its per-package statuses come from the first part of the page. The NVD page returned only a stub. We did not read Anza's thread, the Foundation's message or the Discord post with the exact commands, so their content comes from the outlets that report them. Our Solana data comes from getClusterNodes and getVoteAccounts on the public mainnet-beta RPC on 20 November 2026. Distribution statuses change as vendors publish updates, so check each page before acting.

This article is reporting and analysis, not security or operations advice. Vendor statuses and scores change, and every figure here carries the date it was checked.