VulnerabilityPublished 29 Oct 2024Updated 4 Nov 2025

CVE-2024-50083: Linux kernel · tcp: fix mptcp DSS corruption due to large pmtu xmit

Source GCVE Database

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 29 Oct 2026, 23:30 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-v7pq-vg76-qwqx

What to do

AI-suggested

A fix for this vulnerability has been committed to the Linux kernel. Users and administrators should update to a kernel version that includes this fix once available. Since no specific fixed versions are provided in the data, check the official Linux kernel advisories or vendor patches for the corrected releases. Until patched, affected systems may be vulnerable to denial of service via crafted network traffic exploiting large PMTU transmissions in MPTCP.

Description

CVE-2024-50083 is a high-severity vulnerability in the Linux kernel's Multipath TCP (MPTCP) implementation. It involves a defect causing DSS (Data Sequence Signal) corruption triggered by large Path Maximum Transmission Unit (PMTU) transmissions. The issue was discovered through fuzzing with Syzkaller, which caused kernel warnings and potential instability. This flaw can lead to denial of service by corrupting internal TCP state during MPTCP subflow handling.

Impact

The vulnerability can cause denial of service by corrupting the MPTCP DSS state in the Linux kernel, potentially leading to kernel crashes or instability. It does not impact confidentiality or integrity directly but affects availability of the affected system's TCP networking stack.

Summary

This vulnerability in the Linux kernel affects the MPTCP protocol code, specifically in the function __mptcp_move_skbs_from_subflow. Large PMTU transmissions can cause corruption of the DSS, a critical component for managing data sequencing across multiple TCP subflows. The issue was identified by Syzkaller fuzzing, which triggered kernel warnings and stack traces indicating memory corruption. The flaw can cause kernel instability or crashes due to corrupted TCP state. The vulnerability has a CVSS 3.1 score of 7.5 (high severity) with network attack vector, low attack complexity, no privileges required, and no user interaction needed. No public exploits or known in-the-wild exploitation have been reported. The vulnerability is not in a cloud service and no affected versions are explicitly stated in the provided data.

References

Community reviews

Loading reviews…