What changed, and why it matters
This commit adds release notes for LND versions 0.20.7 and 0.21.6, warning Linux users about a serious Linux kernel security flaw (CVE-2026-98432). The notes explain that recent LND versions accidentally exposed a feature called MPTCP on network ports, which attackers could use to remotely exploit the kernel. The release notes tell operators to upgrade LND, disable MPTCP on their server, and install a patched Linux kernel. The actual code change that disables MPTCP was done in a separate pull request; this commit only documents it and removes a draft release-note fragment.
Treat this documentation commit as a security advisory marker. Linux operators running LND 0.20.x or 0.21.x should upgrade to the patched release, disable MPTCP at the host level (sysctl net.mptcp.enabled=0), verify no MPTCP listeners remain (ss -Mlnp | grep lnd), and install a distribution kernel patch for CVE-2026-98432 as soon as available. Review PR 11456 for the actual code change.
Security signals we found
CVE-2026-98432 referenced as a Linux kernel vulnerability with demonstrated remote exploit
MPTCP listeners identified as the demonstrated exploit path through LND
Vendor urges Linux operators to upgrade LND, disable MPTCP system-wide, and install a patched kernel
Release notes state LND binaries now disable MPTCP listeners by default
Windows and macOS explicitly noted as unaffected
Evidence from the diff
The commit is documentation-only: it creates release-notes-0.20.7.md and release-notes-0.21.6.md and deletes docs/release-notes/unreleased/11456.md. The notes describe CVE-2026-98432 as a Linux kernel vulnerability reachable through MPTCP listeners. Go 1.24+ enables MPTCP by default, so LND 0.20.x/0.21.x on Linux exposed MPTCP on peer, gRPC, and REST ports. The notes state that LND now disables MPTCP listeners by default (via PR 11456), restoring plain TCP and closing the demonstrated exploit path through LND, but a patched kernel is still required because the underlying kernel bug is not MPTCP-specific. The diff itself does not contain the code fix; it only ports the final release notes to master.
Changed components
docs/release-notes/release-notes-0.20.7.mddocs/release-notes/release-notes-0.21.6.mddocs/release-notes/unreleased/11456.mdInspect captured patch +210 / −8
### docs/release-notes/release-notes-0.20.7.md
@@ -0,0 +1,105 @@
+# Release Notes
+- [Bug Fixes](#bug-fixes)
+- [New Features](#new-features)
+ - [Functional Enhancements](#functional-enhancements)
+ - [RPC Additions](#rpc-additions)
+ - [lncli Additions](#lncli-additions)
+- [Improvements](#improvements)
+ - [Functional Updates](#functional-updates)
+ - [RPC Updates](#rpc-updates)
+ - [lncli Updates](#lncli-updates)
+ - [Breaking Changes](#breaking-changes)
+ - [Performance Improvements](#performance-improvements)
+ - [Deprecations](#deprecations)
+- [Technical and Architectural Updates](#technical-and-architectural-updates)
+ - [BOLT Spec Updates](#bolt-spec-updates)
+ - [Testing](#testing)
+ - [Database](#database)
+ - [Code Health](#code-health)
+ - [Tooling and Documentation](#tooling-and-documentation)
+
+### ⚠️ Action required for Linux operators: CVE-2026-98432
+
+[CVE-2026-98432](https://nvd.nist.gov/vuln/detail/CVE-2026-98432) is a Linux
+kernel vulnerability. The [demonstrated remote
+exploit](https://www.openwall.com/lists/oss-security/2026/10/30/1) requires a
+Multipath TCP (MPTCP) listener, which Go 1.24+ enables by default and which lnd
+0.20.x therefore exposed on its peer, gRPC and REST ports. Windows and macOS
+are not affected.
+
+Do all three, in order:
+
+1. **Upgrade to this release.** lnd no longer opens MPTCP listeners, which
+ closes the demonstrated exploit path through lnd.
+2. **Disable MPTCP on the host.** This release does not protect other
+ services on the same machine. Run:
+ ```shell
+ sudo sysctl -w net.mptcp.enabled=0
+ echo 'net.mptcp.enabled = 0' | sudo tee /etc/sysctl.d/90-disable-mptcp.conf
+ ```
+ If the command reports that the key does not exist, your kernel has no
+ MPTCP support and is not exposed through this path. The setting is per
+ network namespace: if lnd runs in Docker, pass
+ `--sysctl net.mptcp.enabled=0` to the container, or use the firewall rule
+ in [issue 11455](https://github.com/lightningnetwork/lnd/issues/11455),
+ which covers all namespaces.
+3. **Install a patched kernel** as soon as your distribution ships one.
+ Disabling MPTCP closes the demonstrated exploit only; the kernel bug is not
+ specific to MPTCP, and the kernel patch is the only fix.
+
+Verify with `sudo ss -Mlnp | grep lnd`, which should print nothing. If you
+cannot upgrade yet, start the existing binary with `GODEBUG=multipathtcp=0`
+instead; see the [pinned
+mitigation](https://github.com/lightningnetwork/lnd/issues/11455#issuecomment-6523668359).
+Do not re-enable MPTCP with `GODEBUG=multipathtcp=1` until your kernel is
+patched.
+
+# Bug Fixes
+
+* lnd binaries now [disable MPTCP listeners by
+ default](https://github.com/lightningnetwork/lnd/pull/11456), restoring plain
+ TCP as the default transport and mitigating the demonstrated
+ CVE-2026-98432 exploit path on vulnerable Linux kernels. Upgrading to a
+ patched kernel is still required to fix the underlying vulnerability. Once
+ the kernel is patched, operators can opt in to MPTCP again with
+ `GODEBUG=multipathtcp=1`.
+
+# New Features
+
+## Functional Enhancements
+
+## RPC Additions
+
+## lncli Additions
+
+# Improvements
+
+## Functional Updates
+
+## RPC Updates
+
+## lncli Updates
+
+## Code Health
+
+## Breaking Changes
+
+## Performance Improvements
+
+## Deprecations
+
+# Technical and Architectural Updates
+
+## BOLT Spec Updates
+
+## Testing
+
+## Database
+
+## Code Health
+
+## Tooling and Documentation
+
+# Contributors (Alphabetical Order)
+
+* Ziggie
### docs/release-notes/release-notes-0.21.6.md
@@ -0,0 +1,105 @@
+# Release Notes
+- [Bug Fixes](#bug-fixes)
+- [New Features](#new-features)
+ - [Functional Enhancements](#functional-enhancements)
+ - [RPC Additions](#rpc-additions)
+ - [lncli Additions](#lncli-additions)
+- [Improvements](#improvements)
+ - [Functional Updates](#functional-updates)
+ - [RPC Updates](#rpc-updates)
+ - [lncli Updates](#lncli-updates)
+ - [Breaking Changes](#breaking-changes)
+ - [Performance Improvements](#performance-improvements)
+ - [Deprecations](#deprecations)
+- [Technical and Architectural Updates](#technical-and-architectural-updates)
+ - [BOLT Spec Updates](#bolt-spec-updates)
+ - [Testing](#testing)
+ - [Database](#database)
+ - [Code Health](#code-health)
+ - [Tooling and Documentation](#tooling-and-documentation)
+
+### ⚠️ Action required for Linux operators: CVE-2026-98432
+
+[CVE-2026-98432](https://nvd.nist.gov/vuln/detail/CVE-2026-98432) is a Linux
+kernel vulnerability. The [demonstrated remote
+exploit](https://www.openwall.com/lists/oss-security/2026/10/30/1) requires a
+Multipath TCP (MPTCP) listener, which Go 1.24+ enables by default and which lnd
+0.21.x therefore exposed on its peer, gRPC and REST ports. Windows and macOS
+are not affected.
+
+Do all three, in order:
+
+1. **Upgrade to this release.** lnd no longer opens MPTCP listeners, which
+ closes the demonstrated exploit path through lnd.
+2. **Disable MPTCP on the host.** This release does not protect other
+ services on the same machine. Run:
+ ```shell
+ sudo sysctl -w net.mptcp.enabled=0
+ echo 'net.mptcp.enabled = 0' | sudo tee /etc/sysctl.d/90-disable-mptcp.conf
+ ```
+ If the command reports that the key does not exist, your kernel has no
+ MPTCP support and is not exposed through this path. The setting is per
+ network namespace: if lnd runs in Docker, pass
+ `--sysctl net.mptcp.enabled=0` to the container, or use the firewall rule
+ in [issue 11455](https://github.com/lightningnetwork/lnd/issues/11455),
+ which covers all namespaces.
+3. **Install a patched kernel** as soon as your distribution ships one.
+ Disabling MPTCP closes the demonstrated exploit only; the kernel bug is not
+ specific to MPTCP, and the kernel patch is the only fix.
+
+Verify with `sudo ss -Mlnp | grep lnd`, which should print nothing. If you
+cannot upgrade yet, start the existing binary with `GODEBUG=multipathtcp=0`
+instead; see the [pinned
+mitigation](https://github.com/lightningnetwork/lnd/issues/11455#issuecomment-6523668359).
+Do not re-enable MPTCP with `GODEBUG=multipathtcp=1` until your kernel is
+patched.
+
+# Bug Fixes
+
+* lnd binaries now [disable MPTCP listeners by
+ default](https://github.com/lightningnetwork/lnd/pull/11456), restoring plain
+ TCP as the default transport and mitigating the demonstrated
+ CVE-2026-98432 exploit path on vulnerable Linux kernels. Upgrading to a
+ patched kernel is still required to fix the underlying vulnerability. Once
+ the kernel is patched, operators can opt in to MPTCP again with
+ `GODEBUG=multipathtcp=1`.
+
+# New Features
+
+## Functional Enhancements
+
+## RPC Additions
+
+## lncli Additions
+
+# Improvements
+
+## Functional Updates
+
+## RPC Updates
+
+## lncli Updates
+
+## Code Health
+
+## Breaking Changes
+
+## Performance Improvements
+
+## Deprecations
+
+# Technical and Architectural Updates
+
+## BOLT Spec Updates
+
+## Testing
+
+## Database
+
+## Code Health
+
+## Tooling and Documentation
+
+# Contributors (Alphabetical Order)
+
+* Ziggie
### docs/release-notes/unreleased/11456.md
@@ -1,8 +0,0 @@
-# Bug Fixes
-
-* lnd binaries now [disable MPTCP listeners by
- default](https://github.com/lightningnetwork/lnd/pull/11456), restoring plain
- TCP as the default transport and mitigating the demonstrated
- CVE-2026-98432 exploit path on vulnerable Linux kernels. Operators can opt
- in to MPTCP with `GODEBUG=multipathtcp=1`; upgrading to a patched kernel is
- still required to fix the underlying vulnerability.Why this scored 79/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.