CVE-2024-50185

What it actually does

The vulnerability permits bugged peers to transmit corrupted DSS options in MPTCP connections, triggering inconsistent warning splats and error paths in the kernel data plane instead of uniform DEBUG_NET assertions, MIB dumps, fallback, or reset handling.

Why it matters to the business

Organizations running Linux kernels with MPTCP face potential connection instability, kernel log noise, or subflow resets across 348 downstream dependents, increasing operational overhead for network-reliant services without ransomware or KEV urgency.

How an attack unfolds

An attacker using a bugged or malicious peer implementation establishes an MPTCP session and repeatedly sends corrupted DSS options to hit the vulnerable data-path warnings, forcing fallback or reset behavior according to subflow type.

How to fix it

Update the Linux kernel to include commit fde99e972b8f88cebe619241d7aa43d288ef666a or an equivalent fixed version that applies DEBUG_NET assertions and consistent error handling for DSS corruption.

How to confirm the fix worked

Confirm the running kernel contains the referenced commit, enable DEBUG_NET assertions, and verify that corrupted DSS traffic now produces MIB updates without prior warning splats.

Typical attack path

1. Initiate MPTCP connection with a remote peer
2. Transmit consistently malformed DSS options
3. Trigger kernel data-path warnings and MIB updates
4. Force subflow fallback or connection reset

How to detect it

Inspect kernel logs for MPTCP DSS-related warnings, unexpected MIB increments, and subflow fallback or reset events; correlate with network traffic containing anomalous DSS options.

What your security team should do

• Prioritize kernel upgrade to the fixed commit on all MPTCP-enabled systems
• Review MPTCP-related kernel logs and MIB counters for prior anomalies
• Test fallback behavior in a lab environment before production rollout