LND Disables Multipath TCP Listeners After Kernel Flaw

Lightning node software closes an attack route tied to CVE-2026-98432 while the underlying Linux kernel flaw remains unpatched on affected systems.

Updated on Nov. 9, 2026 in Cybersecurity

Bold flat-color editorial illustration of centered server racks linked by a single crimson cable to a plain network switch, in navy and cream.
Lightning node software maker LND on October 30 disabled Multipath TCP listeners by default, blocking a demonstrated attack route while the Linux kernel flaw CVE-2026-98432 remains unpatched. AI Illustration. Upload story photo >

LND v0.20.7-beta and v0.21.6-beta, released October 30, disable Multipath TCP listeners by default. The change closes a demonstrated route through those listeners but leaves the Linux kernel flaw CVE-2026-98432 in place.

Why it matters

The kernel flaw, which involves freed memory being used during IPv4 TCP connection handling, is rated critical at 9.8 by Ubuntu. Systems without exposed MPTCP listeners may still face similar attacks, so the software workaround does not remove the underlying risk.

Ubuntu rates CVE-2026-98432 at a CVSS 3.1 score of 9.8, and LND's releases v0.20.7-beta and v0.21.6-beta disable MPTCP listeners by default. The Ubuntu tracker still lists the standard linux package for Ubuntu 24.04 LTS as vulnerable, while Ubuntu 26.10 is shown fixed in 7.3.0-10.10.

The players

Canonical

Canonical is the company behind Ubuntu, the Linux distribution whose security tracker rates CVE-2026-98432 and whose kernel packages are affected.

LND

LND is the Lightning Network Daemon, a widely used Lightning Network node implementation whose recent releases disabled Multipath TCP listeners.

The details

LND's October 30 releases disable Multipath TCP listeners by default, closing the demonstrated attack route, which requires an exposed MPTCP listener. Go 1.24 and later enabled MPTCP listeners by default on Linux, which LND 0.21.x exposed on its peer, gRPC and REST ports. Canonical said kernel fixes were available in its -proposed repository on November 2, and Core Lightning channel and remote-command fixes were reported on November 6.

Timeline

  1. October 30: LND v0.20.7-beta and v0.21.6-beta releases disable MPTCP listeners by default.

  2. November 2: Canonical says kernel fixes are available in the -proposed repository.

  3. November 6: Core Lightning channel and remote-command fixes are reported.

  4. November 7: The Ubuntu tracker is last updated.

  5. November 9: The Ubuntu tracker is checked and still shows vulnerable status for affected packages.

The Tech Race

The story extends the default-on MPTCP behavior introduced in Go 1.24, which exposed LND 0.21.x listeners on peer, gRPC and REST ports. LND's October 30 release reverses that exposure at the application level, while the underlying kernel flaw CVE-2026-98432 remains unpatched on affected Linux systems.

Users running LND nodes should upgrade to v0.20.7-beta or v0.21.6-beta to disable exposed MPTCP listeners. Operators of Ubuntu 22.04 or 24.04 systems should watch for kernel updates, since the standard packages remained flagged vulnerable on November 9.

The takeaway

A software-level workaround can close a specific attack path without fixing the kernel flaw beneath it. Operators should treat the LND update and any Ubuntu kernel patch as separate steps.

What happens next

Ubuntu has not yet confirmed a completed fix for the 24.04 and 22.04 kernel packages as of the last tracker check, so further tracker updates will determine when the flaw is resolved.

Further reading

Track related vulnerability coverage in the Cybersecurity section.