Peter, the host of the Learn Crypto Podcast, explained why the Linux kernel use-after-free CVE-2026-98432 puts exposed Cardano stake pool relays at risk, and what operators can do while their distribution is still without a fix.
Podcasts ·
Peter, the host of the Learn Crypto Podcast, walked through the Linux kernel vulnerability CVE-2026-98432 on the episode Critical Linux CVE Puts Cardano Stake Pools on Alert (2 November 2026). He explained why a race in the kernel's IPv4 TCP handling matters to Cardano stake pool operators, whose relays sit exposed to the internet, and what operators can do while Ubuntu, the distribution he called the main concern, is still without a fix.
Peter described the bug as a timing mistake: "So one part of the kernel can throw that note away while the other part is still trying to read it." (from 0:02:53) The note in question is the extra connection detail Linux keeps during a TCP handshake, and the trigger needs no credentials: "So an attack can hit at that very moment by sending a carefully timed connection request with no password needed." (from 0:02:53)
The exposure for Cardano is the relay: "So this particular attack can attack the relays because they're exposed to the internet and could potentially crash them." (from 0:03:48) With its relays down, a pool can still make blocks but cannot get them to the rest of the network. In the worst case, he said, an attacker who takes control of a relay learns where the block producer is, because the relay has to connect to it: "It will know the IP address between the relay and the block producer, so it will know that relationship." (from 0:04:44) Delegators' coins are not what is exposed: "Now, if you're a delegator, your ADA stays in your wallet. It never goes to the stake pool." (from 0:04:44) What an attacker could go after, he said, is the pool's keys, potentially its pledged ADA, and its ability to make blocks.
For operators, Peter passed on the advice in Intersect's weekly update: check which kernel the block producer and relays run, and apply the fixed kernel as soon as the distribution publishes it, remembering that it does no good until the machine reboots: "The fix doesn't work until you reboot." (from 0:06:39) The interim measures only narrow the window: "Until then, you can turn off MPTCP if you don't use it and add a firewall rule that drops TCP packets carrying IPv4 options." (from 0:06:39) "That only reduces your exposure. It doesn't fix the bug, so you still need to patch." (from 0:06:39)
The National Vulnerability Database record for CVE-2026-98432 confirms the mechanics Peter described: a race in the handling of TCP connection requests that frees the IPv4 options block while another CPU can still read it, carrying a 9.8 Critical score from the reporting CNA while NVD's own analysis is pending, affecting kernels from version 4.4 and fixed in 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10 and 7.3: NVD: CVE-2026-98432.
Peter relayed a news report that Anthropic's Claude had built a private proof of concept that gets root on servers with an MPTCP listener, adding that the outlet could not verify the claim. Anthropic's own disclosure bears it out: "Claude wrote an exploit that allows a remote attacker to send packets to Linux servers with a multipath TCP listener to run arbitrary commands as root, without any credentials or user interaction" (Anthropic, 27 October 2026). The same write-up describes the two stages, defeating KASLR and then overwriting a callback pointer, and gives the timings in its proof of concept: 48 minutes to leak a kernel pointer and five more minutes to run a shell command: Discovering and exploiting vulnerabilities in critical, real-world software with Claude.
On patch status, Peter listed Debian, Red Hat, SUSE Enterprise, Oracle and Amazon Linux as already patched, and said Ubuntu had no fix at the time of recording, 2 November. CSO Online reported that fixed kernel packages were available for at least some releases of Debian, Oracle Linux, SUSE and Amazon Linux, while Ubuntu and Red Hat Enterprise Linux had yet to release patched kernels as of 30 October. Ubuntu's own tracker, as of 7 November 2026, lists the kernel as fixed in 26.10, still vulnerable with a fix in progress in every LTS release from 16.04 to 26.04, and not affected in 14.04 LTS. Its mitigation section gives the same interim measure, a user-contributed rule that drops incoming IPv4 TCP packets carrying IP options, which it says reduces the risk but does not fully prevent exploitation: Ubuntu: CVE-2026-98432.
This page was written from an episode in Alphaday’s podcast feed. Its record, with the audio file, the episode page and a description, is one call away. Free, no signup, no key.
Start building with the podcasts API
Track what the shows say about a project, from each episode's description.
The podcast feed as tools, for Claude, Cursor and any MCP client.
The stories the shows are reacting to.
Quotes are from machine transcripts of the episodes, with misheard names corrected, and each timestamp is where its passage starts. What a guest says is their claim; the sources linked beside it are what it was checked against.