CVE-2022-50071: mptcp: move subflow cleanup in mptcp_destroy_common()
In the Linux kernel, the following vulnerability has been resolved:
mptcp: move subflow cleanup in mptcp_destroy_common()
If the mptcp socket creation fails due to a CGROUP_INET_SOCK_CREATE
eBPF program, the MPTCP protocol ends-up leaking all the subflows:
the related cleanup happens in __mptcp_destroy_sock() that is not
invoked in such code path.
Address the issue moving the subflow sockets cleanup in the
mptcp_destroy_common() helper, which is invoked in every msk cleanup
path.
Additionally get rid of the intermediate list_splice_init step, which
is an unneeded relic from the past.
The issue is present since before the reported root cause commit, but
any attempt to backport the fix before that hash will require a complete
rewrite.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can leak MPTCP subflow sockets when socket creation fails because of a CGROUP_INET_SOCK_CREATE eBPF program. The source does not provide a severity score or confirmed business impact, but kernel resource leaks can create operational stability risk.
Executive priority
Treat as a targeted kernel maintenance issue unless your environment depends on MPTCP and cgroup eBPF controls. Prioritize routine kernel patching, with higher urgency for systems matching that feature combination.
Technical view
The cleanup for MPTCP subflows was in __mptcp_destroy_sock(), which is not reached on one failed socket-creation path. The fix moves subflow socket cleanup into mptcp_destroy_common(), a common cleanup helper reached across cleanup paths.
Likely exposure
Exposure is most relevant to Linux systems using MPTCP where cgroup eBPF socket-create programs can reject socket creation. The source lists Linux kernel versions including 5.11, 5.19.4, and 6.0 as affected, with stable kernel commits provided as references.
Exploitation context
The CVE bundle marks KEV as false and provides no evidence of active exploitation. The described trigger depends on a specific kernel networking and eBPF interaction, not a generic remote attack path in the provided evidence.
Researcher notes
The source is precise about root cause and cleanup path but does not include CVSS, CWE, exploitability details, or impact quantification. Avoid assuming remote exploitability or privilege requirements beyond the stated MPTCP and eBPF failure path.
Mitigation direction
Update to a Linux kernel containing the referenced stable fixes.
Check distribution vendor advisories for backported kernel packages.
Prioritize systems using MPTCP with cgroup eBPF socket-create programs.
If patching is delayed, review whether the affected feature combination is necessary.
Validation and detection
Inventory kernel versions across Linux hosts and appliances.
Identify hosts with MPTCP enabled or in active use.
Review cgroup eBPF socket-create program usage on exposed systems.
Confirm installed kernel packages include the referenced upstream fixes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50071 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.