Local availability loss via MPTCP endpoint misaccounting
Published Mar 25, 2026 · Updated Mar 25, 2026
Incorrect endpoint accounting in the Linux kernel MPTCP path manager allows local users to disrupt availability during endpoint removal. When signaling clears an endpoint's availability bit without creating a subflow, mptcp_pm_create_subflow_or_signal_addr leaves local_addr_used at zero, and later removal reaches an invalid accounting assumption. The trigger requires local access, a zero subflow limit, a signal-and-subflow endpoint, a connection from another address, and endpoint removal.
Summary
What happened
Incorrect endpoint accounting in the Linux kernel MPTCP path manager allows local users to disrupt availability during endpoint removal. When signaling clears an endpoint's availability bit without creating a subflow, mptcp_pm_create_subflow_or_signal_addr leaves local_addr_used at zero, and later removal reaches an invalid accounting assumption. The trigger requires local access, a zero subflow limit, a signal-and-subflow endpoint, a connection from another address, and endpoint removal.
The record
- CVE
- CVE-2026-23321
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0f21cc29bc13e86512621727a4388c8a7ad2716b
- Affected versionversion=6.11
- Affected versionversion=64815ba15880ce5f99df075fa4104fef170ac7e5 <05799c2f1ca5eb13d65764dda688d02021b65e06
- Affected versionversion=85df533a787bf07bf4367ce2a02b822ff1fba1a3 <198824ccfa64ffebd918bf99c939bd8170a4a4d8
- Affected versionversion=85df533a787bf07bf4367ce2a02b822ff1fba1a3 <579a752464a64cb5f9139102f0e6b90a1f595ceb
- Affected versionversion=85df533a787bf07bf4367ce2a02b822ff1fba1a3 <67f34ab318807989b57dfdb0f79e2d4e57018290
- Affected versionversion=85df533a787bf07bf4367ce2a02b822ff1fba1a3 <a64aa7db39392add5be09dffaedbf1f0ce5554df
- Affected versionversion=d93cf38fad9f66397093432b8917971a92ee0146 <c5c877e140e5f46023a74a51e577ce5edd0a4be7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo