[DPDK/other Bug 2153] ip_frag: all IPV6 fragments have ID of zero

bugzilla at dpdk.org bugzilla at dpdk.org
Fri Nov 20 19:43:19 CET 2026


https://bugs.dpdk.org/show_bug.cgi?id=2153

            Bug ID: 2153
           Summary: ip_frag: all IPV6 fragments have ID of zero
           Product: DPDK
           Version: 26.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev at dpdk.org
          Reporter: stephen at networkplumber.org
  Target Milestone: ---

TLDR; all IPV6 fragments go out with id of 0 which can lead to botched
reassembly at receiver.


============================================================================
ANT-2026-70V47B5Y  [low]  CWE-340  logic
ip_frag: constant IPv6 fragment ID allows off-path fragment injection
Location: lib/ip_frag/rte_ipv6_fragmentation.c:34  in __fill_ipv6hdr_frag()
Commit:   9a45341f18a1ab47af7123e63d942b90c1b79f38
=========

`rte_ipv6_fragment_packet()` puts Identification 0 in the fragment header of
every fragment of every packet, so receivers cannot tell apart fragments of
different packets sent between the same two addresses. An off-path sender who
knows the two addresses and can spoof the source address can send one forged
"last fragment" with Identification 0, with nothing to guess. That fragment
replaces the tail of the next fragmented datagram, and each datagram after it
is then completed with its predecessor's tail. The DPDK process itself is not
affected; the harm falls on the receiver of the IPv6 traffic the application
fragments.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the dev mailing list