LND update blocks one Lightning exploit route, but critical Linux kernel flaw remains

Editorial illustration: A silver machine with blue-lit cables, a bolted front panel and a lightning bolt sits on a dark pedestal bearing a penguin emblem. An orange-glowing crack splits the pedestal.

In brief

  • LND v0.20.7-beta and v0.21.6-beta disable Multipath TCP (MPTCP) listeners by default.
  • CVE-2026-98432: the update closes one demonstrated exploit route, but the Linux kernel flaw remains.
  • Ubuntu rates the Linux kernel bug critical, with a CVSS 3.1 score of 9.8.
  • Advisories describe a demonstrated exploit, not attacks on LND nodes or stolen bitcoin.

What the LND release fixes (and what it doesn't)

LND's operator notes say Go 1.24 and later turned on MPTCP listeners by default on Linux, which LND 0.21.x then exposed on its peer, gRPC and REST ports. The new releases switch those listeners off.

That shuts one door. Not all of them.

The kernel flaw itself stays in place, and the update doesn't cover other services on the same machine. If another exposed MPTCP service runs on an unpatched host, the demonstrated route can stay open even after LND's default change. The bug involves freed memory being used during IPv4 TCP connection handling in Linux, and it can let an attacker run code on an affected host. Ubuntu gives it a critical CVSS 3.1 score of 9.8.

The Go team says the bug is broader

The Go Security Team's advisory said the demonstrated exploit needs an exposed MPTCP listener, but the kernel bug goes further. Similar attacks against systems without MPTCP listeners may be possible, according to the advisory (it doesn't establish a demonstrated non-MPTCP exploit). Go also warned that disabling MPTCP one program at a time is fragile: a single leftover exposed listener keeps the system vulnerable, and explicit socket settings can override Go's default.

It's a demonstrated Linux exploit, not evidence that attackers used the flaw against LND nodes or stole bitcoin. The Core Lightning channel and remote-command fixes reported November 6 concern separate application flaws.

Kernel patch status varies by package

The Ubuntu tracker, checked November 9 and last updated November 7, still labeled the standard linux package for Ubuntu 24.04 LTS vulnerable, with work in progress in 6.8.0-149.149. The 22.04 LTS entry carried the same status for 5.15.0-203.213, while the standard 26.10 package was listed as fixed in 7.3.0-10.10. Cloud, hardware-enablement and other kernel variants have separate entries.

Canonical said in a November 2 advisory that fixes were available in the -proposed repository for users who run their own kernel acceptance tests, while qualification testing continued. Ubuntu's newsletter for November 1–7 said some releases, including 24.04, had advanced to -updates, without identifying every kernel variant.

Operators need to check the update for their exact kernel package. LND maintainers recommend upgrading the application, disabling MPTCP on the host and installing a patched kernel as soon as the distribution makes one available. LND's update changes the app; repairing the shared Linux kernel requires a separate host update.

Frequently asked questions

Does upgrading LND fully protect a Lightning node from CVE-2026-98432?

No. LND's October 30 releases disable MPTCP listeners by default, which closes the demonstrated route through LND's listeners. The kernel flaw stays in place, and another exposed MPTCP service on the same unpatched machine can keep that route open.

What do LND maintainers recommend operators do?

LND maintainers recommend upgrading the application, disabling MPTCP on the host, and installing a patched kernel as soon as the distribution makes one available. The kernel repair is a separate host update from the LND upgrade.

Have attackers used this flaw against LND nodes?

The advisories describe a demonstrated Linux exploit, not evidence that attackers used the flaw against LND nodes or stole bitcoin. The Go Security Team said similar attacks without MPTCP listeners may be possible, but no non-MPTCP exploit has been demonstrated.