Skip to main content

CVE-2024-50083: Vulnerability in Linux Linux

High
VulnerabilityCVE-2024-50083cvecve-2024-50083
Published: Tue Oct 29 2024 (10/29/2024, 00:50:26 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: tcp: fix mptcp DSS corruption due to large pmtu xmit Syzkaller was able to trigger a DSS corruption: TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Modules linked in: CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 <0f> 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff RSP: 0018:ffffc90000006db8 EFLAGS: 00010246 RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00 RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0 RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8 R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000 R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5 FS: 000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> move_skbs_to_msk net/mptcp/protocol.c:811 [inline] mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854 subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490 tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283 tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350 ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 __netif_receive_skb_one_core net/core/dev.c:5662 [inline] __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6107 __napi_poll+0xcb/0x490 net/core/dev.c:6771 napi_poll net/core/dev.c:6840 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6962 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 do_softirq+0x11b/0x1e0 kernel/softirq.c:455 </IRQ> <TASK> __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline] __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451 dev_queue_xmit include/linux/netdevice.h:3094 [inline] neigh_hh_output include/net/neighbour.h:526 [inline] neigh_output include/net/neighbour.h:540 [inline] ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236 ip_local_out net/ipv4/ip_output.c:130 [inline] __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536 __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline] tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752 __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015 tcp_push_pending_frames include/net/tcp.h:2107 [inline] tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline] tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 sk_backlog_rcv include/net/sock.h:1113 [inline] __release_sock+0x214/0x350 net/core/sock.c:3072 release_sock+0x61/0x1f0 net/core/sock.c:3626 mptcp_push_ ---truncated---

AI-Powered Analysis

AILast updated: 07/04/2025, 02:11:58 UTC

Technical Analysis

CVE-2024-50083 is a vulnerability identified in the Linux kernel's implementation of Multipath TCP (MPTCP), specifically related to the handling of Data Sequence Signal (DSS) corruption caused by large Path Maximum Transmission Unit (PMTU) transmissions. MPTCP is an extension of TCP that allows a single connection to use multiple paths to maximize resource usage and increase redundancy. The vulnerability arises in the function __mptcp_move_skbs_from_subflow within the net/mptcp/protocol.c source file, where improper handling of socket buffers (skbs) during subflow data movement can lead to DSS corruption. This corruption was triggered by the Syzkaller fuzzing tool, which also generated kernel warnings indicative of potential SYN flooding and kernel stack traces pointing to the problematic code path. The issue is related to TCP request socket subflow handling and the transmission of large packets exceeding PMTU, which can cause memory corruption or data integrity issues within the MPTCP stack. The vulnerability does not have a publicly available CVSS score and no known exploits in the wild have been reported as of the publication date (October 29, 2024). The affected Linux kernel versions are identified by commit hashes, indicating that this is a recent and specific code regression or flaw. The vulnerability could potentially allow attackers to cause denial of service (DoS) conditions by triggering kernel warnings and corrupting TCP data sequences, impacting network reliability and stability on affected systems running MPTCP-enabled Linux kernels.

Potential Impact

For European organizations, the impact of CVE-2024-50083 could be significant, especially for those relying on Linux-based infrastructure that utilizes MPTCP for enhanced network performance and redundancy. This includes cloud service providers, telecommunications companies, financial institutions, and enterprises with critical network operations. The vulnerability could lead to kernel crashes or instability, resulting in denial of service that disrupts network communications. Given that MPTCP is often used in environments requiring high availability and fault tolerance, such as data centers and multi-homed network setups, exploitation could degrade service quality or cause outages. While no known exploits exist currently, the potential for attackers to induce DSS corruption and SYN flooding warnings suggests a risk of targeted DoS attacks. Confidentiality and integrity impacts appear limited as the vulnerability primarily affects data handling within the kernel rather than exposing data externally. However, availability impacts could be severe, affecting business continuity and operational reliability.

Mitigation Recommendations

To mitigate CVE-2024-50083, European organizations should: 1) Immediately apply the latest Linux kernel patches that address the MPTCP DSS corruption issue once they become available from trusted Linux distributions or kernel maintainers. 2) Temporarily disable MPTCP functionality if it is not critical to operations, reducing the attack surface until patches are applied. 3) Monitor network traffic and kernel logs for unusual SYN flooding warnings or kernel warnings related to MPTCP subflows, which could indicate attempted exploitation. 4) Employ network segmentation and rate limiting on TCP ports commonly used for MPTCP to limit potential attack vectors. 5) Engage with Linux distribution vendors and maintain an up-to-date inventory of kernel versions deployed across infrastructure to ensure timely patch management. 6) Conduct internal testing in controlled environments to verify patch effectiveness and assess any operational impacts before wide deployment. 7) Consider deploying intrusion detection systems tuned to detect anomalies in TCP subflow behavior or kernel-level network stack anomalies.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-10-21T19:36:19.942Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9824c4522896dcbdfec5

Added to database: 5/21/2025, 9:08:52 AM

Last enriched: 7/4/2025, 2:11:58 AM

Last updated: 7/27/2025, 7:50:50 AM

Views: 9

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats