CVE-2026-80784
Received Received - Intake

Memory Leak in Linux Kernel MPTCP Protocol

Vulnerability report for CVE-2026-80784, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-04

Last updated on: 2026-09-04

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: fix memory leak from alloc-during-teardown race mptcp_pm_destroy() empties msk->pm.anno_list and msk->pm.userspace_pm_local_addr_list under msk->pm.lock during socket teardown, dropping the lock between the two. A concurrent userspace PM genl ANNOUNCE on the same msk holds a sock reference via mptcp_token_get_sock() and, in mptcp_pm_nl_announce_doit(), calls mptcp_userspace_pm_append_new_local_addr() and mptcp_pm_announced_alloc(). Both take msk->pm.lock briefly to add to their respective lists. Because the genl handler holds a sock reference, mptcp_pm_destroy() may run on the same msk via mptcp_disconnect(), which invokes mptcp_destroy_common() without dropping the sock refcount, before the handler completes. If the lock acquisitions interleave such that mptcp_pm_destroy() empties a list first, the later alloc adds its entry to a list head that nothing else iterates for this msk, and the entry leaks. kmemleak reports both mptcp_pm_add_addr objects (from mptcp_pm_announced_alloc()) and mptcp_pm_addr_entry objects (from mptcp_userspace_pm_append_new_local_addr()) under sustained concurrent ANNOUNCE + close load against the userspace PM. Add an MPTCP_PM_DESTROYING bit in msk->pm.status, set by mptcp_pm_destroy() under pm.lock before the lists are emptied and checked under pm.lock by the alloc paths. Either the alloc takes pm.lock first, in which case its entry is on the list when mptcp_pm_destroy() frees it; or mptcp_pm_destroy() takes pm.lock first, in which case the later alloc observes the bit and refuses. Found by an MPTCP protocol-flow harness extending BRF (arXiv:2305.08782).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-04
Last Modified
2026-09-04
Generated
2026-09-04
AI Q&A
2026-09-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a memory leak vulnerability in the Linux kernel's Multipath TCP (MPTCP) implementation. It occurs during socket teardown when concurrent operations interfere with each other. Specifically, a race condition between userspace PM (Path Manager) operations and socket destruction can cause memory allocated for MPTCP addresses to leak because cleanup processes are interrupted by new allocations.

Detection Guidance

This vulnerability is specific to the Linux kernel's MPTCP (Multipath TCP) implementation and involves a memory leak during socket teardown. Detection requires kernel-level monitoring for memory leaks in MPTCP-related structures. Check for kmemleak reports or use tools like 'cat /sys/kernel/debug/kmemleak' to identify leaks. Monitor system logs for MPTCP-related errors or crashes. No direct network commands are applicable as this is a local kernel issue.

Impact Analysis

The impact is primarily on system stability and resource usage. Memory leaks can gradually consume available memory, leading to performance degradation or system crashes over time. This is particularly problematic for systems running long-lived MPTCP connections under sustained concurrent operations.

Compliance Impact

This vulnerability is a memory leak in the Linux kernel's MPTCP protocol implementation. It does not directly affect compliance with standards like GDPR or HIPAA, as those focus on data protection, privacy, and security controls rather than kernel memory management issues.

Mitigation Strategies

Apply the latest kernel patches or updates that address this specific issue. If patches are unavailable, consider disabling MPTCP functionality if not required, using 'sysctl -w net.mptcp.enabled=0'. Monitor for unusual memory usage patterns in MPTCP-related processes. Restrict access to MPTCP-related network operations if possible.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80784. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart