Bitcoin Core and Lightning developer Matt Corallo warned on Oct. 30 that a severe Linux kernel vulnerability could affect Linux systems running LND, and he criticized Ubuntu for what he described as a slow response to the issue. Corallo called it 「the most critical Linux vuln ever」.

The bug is tracked as CVE-2026-98432. It affects the kernel’s IPv4 TCP handshake code and carries a CVSS severity score of 9.8. Anthropic’s Frontier Red Team later showed that the flaw could be turned into a remote root exploit on systems that expose a Multipath TCP, or MPTCP, listener.
Peter Todd issued a warning the same day, advising anyone running LND on Linux with open ports to shut down their Bitcoin Lightning nodes until the kernel had been patched or another mitigation was in place.
How the demonstrated exploit path reached LND
The exploit path that was publicly demonstrated depends on an MPTCP listener. Go 1.24 and later enable that feature by default. Because LND is written in Go, recent versions were listening with MPTCP on their peer, gRPC, and REST ports whenever the kernel had the feature enabled.
Lightning Labs responded that same day with emergency releases: lnd v0.21.6-beta and the backport v0.20.7-beta. Both releases disable MPTCP listeners by default, which closes the demonstrated exploit path through LND.
The project said the change is a mitigation, not a fix. Lightning Labs noted that only a patched kernel fully resolves the underlying issue. Other services on the same machine can still remain exposed until MPTCP is disabled across the host or the kernel is updated.
Olaoluwa Osuntokun and the official Lightning Labs account both recommended that users update.
Scanning activity and patch rollout across distributions
Security researcher Marcus Hutchins later reported internet-wide scanning activity that matched attempts to find exposed systems. His scans found roughly 2.1 million servers reachable over MPTCP on port 443.
International Cyber Digest highlighted that finding on Nov. 4 and also pointed to the scanning activity and Ubuntu’s slower patch timeline.
Canonical has since made fixed kernels available in the opt-in proposed pocket for Ubuntu 22.04, 24.04, and 26.04, though those updates have not yet reached the regular updates channel. Red Hat shipped fixes for RHEL 8, 9, and 10 on Nov. 1. Debian, Amazon Linux, and other distributions had already released patches earlier.
UmbrelOS 2.0.1 included the kernel fix on Nov. 1 for x86 devices. On Raspberry Pi, where a fixed kernel was not yet available at the time, the project applied a traffic-blocking mitigation.
What is known about current risk
There have been no confirmed reports of in-the-wild exploitation so far, and the vulnerability has not been added to CISA’s Known Exploited Vulnerabilities catalog. Anthropic’s remote-root demonstration has not been published.
In practical terms, the highest exposure is on internet-facing servers. Home desktop systems behind typical NAT and firewalls, without public TCP listeners, are much less affected.
For Lightning operators on Linux, the new LND releases remove the specific MPTCP listener path used in the public exploit, but the broader kernel flaw remains until a patched kernel is installed.
This article first appeared on Bitcoin Magazine and was written by Juan Galt.


