Cross Layer State Desynchronization in Path MTU Discovery

25 concepts10 papers

The internet’s architecture relies on a strict separation of concerns between layers. The network layer (IP) handles routing and packet delivery, while the transport layer (TCP) manages end-to-end reliability. However, this modularity creates a "semantic gap": if one layer receives information about the network path that the other layer does not, the resulting desynchronization can be exploited to hijack connections, bypass security filters, or crash systems.

The Myth of Fragmentation Immunity

For years, the networking community operated under the assumption that TCP was largely immune to IP fragmentation attacks. This belief stemmed from Path MTU Discovery (PMTUD), a mechanism where hosts send packets with the "Don't Fragment" (DF) flag set. If a packet encounters a router with a Maximum Transmission Unit (MTU) smaller than the packet size, the router drops it and sends back an ICMP "Fragmentation Needed" message. The host then shrinks its TCP segments to fit the path, avoiding fragmentation entirely.

As Li et al. demonstrate, this immunity is an illusion. The authors show that off-path attackers can exploit the interaction between ICMP and TCP to force fragmentation even when PMTUD is active. By sending forged ICMP error messages that contain non-TCP payloads (such as ping responses), an attacker can trick the network layer into updating its path MTU while the transport layer remains unaware. This creates a state of cross-layer desynchronization: the transport layer continues to send large segments, which the network layer is then forced to fragment to meet the new, falsely lowered MTU.

Exploiting the Semantic Gap

Once fragmentation is forced, the fundamental security properties of the connection begin to erode. Li et al. explain that this allows attackers to bypass sequence number protections. Because fragments are reassembled by the victim's network stack before being passed to the transport layer, an attacker can inject malicious data fragments that the stack incorrectly merges into the legitimate stream.

This desynchronization also creates side channels. Feng et al. discovered that when a server is tricked into clearing the DF flag via forged ICMP messages, it often changes its packet identification (IPID) assignment logic. To prevent tracking, modern Linux kernels use secure per-socket IPIDs; however, when fragmentation is enabled, the system may revert to a vulnerable global counter. The authors show that an off-path attacker can monitor this global counter to infer secret TCP sequence numbers, enabling connection hijacking with high success rates.

The Failure of Connection Isolation

A critical design flaw in PMTUD is that it typically operates on a per-IP address basis rather than a per-connection basis. In modern network environments where many devices share a single IP—such as NAT gateways, public Wi-Fi, or VPNs—this lack of isolation is catastrophic.

Feng et al. argue that because PMTUD state is shared across all connections from a single IP, an attacker can influence the traffic of one user by sending control messages targeting another. Similarly, Feng et al. describe how this shared state allows attackers to identify NAT devices. By inducing an MTU update that the client accepts but the gateway ignores, attackers can detect the resulting packet fragmentation patterns to map internal network structures and terminate active connections.

Resource Exhaustion and Logic Errors

Beyond data injection, fragmentation-based attacks exploit the reassembly logic of the target's network stack to cause Denial of Service (DoS). Amit Kumar notes that malformed or overlapping fragments can force operating systems into infinite loops or system crashes by exploiting how the stack validates data structures.

In resource-constrained environments like the Internet of Things (IoT), these vulnerabilities are even more acute. Houbing Herbert Song highlights that many low-power protocols cannot verify the authenticity of individual fragments until the entire packet is reassembled. Attackers can exploit this by flooding a device with spoofed fragments, exhausting its limited memory buffers and preventing legitimate traffic from being processed.

Even specialized systems are not immune; Salkield et al. demonstrated that ground station software for satellites can be crashed by injecting packets with non-standard lengths, as legacy tools often rely on hardcoded assumptions about packet size that fragmentation disrupts.

Summary of the Threat Landscape

The research across these papers suggests that fragmentation is not merely a functional tool for handling path constraints, but a significant security boundary. The core issues identified include:

  • Unauthenticated Control Messages: The reliance on unauthenticated ICMP messages allows off-path attackers to manipulate path state (Feng et al.).
  • Infrastructure Constraints: Intermediate routers with small MTUs can force fragmentation regardless of end-host configuration, undermining PMTUD (Li et al.).
  • Reassembly Vulnerabilities: The delay between receiving fragments and verifying the full packet creates windows for buffer overflows and logic exploitation (Song, Varghese).

Key Foundational Work

Detecting evasion attacks at high speeds without reassembly (2006) — contributed 1 concept elements to this direction.
Lightweight IP Traceback Mechanism (2007) — contributed 1 concept elements to this direction.
History & citationVersion 2 · 2026-10-04

Current · Permanent link

  1. Version 2 (latest) · 2026-10-04 · 10 papers
  2. Version 1 · 2026-10-04 · 13 papers
Cite this direction

Latest version (a living page):

@misc{lacuna_fragmentation_based_denial_of_service_cf36265a,
  title = {fragmentation-based denial of service},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/fragmentation-based-denial-of-service/rdr_cf36265a405c453180fd436ccb344be2},
  note = {Latest version of a living research direction; cite a version for a fixed text. Accessed 2026-11-20},
}

This exact version (version 2, frozen text):

@misc{lacuna_fragmentation_based_denial_of_service_cf36265a_v2,
  title = {fragmentation-based denial of service},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/fragmentation-based-denial-of-service/rdr_cf36265a405c453180fd436ccb344be2/v/2},
  note = {Version 2, frozen 2026-10-04. Accessed 2026-11-20},
}

See something wrong? Report a mistake