From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 2153] ip_frag: all IPV6 fragments have ID of zero
Date: Fri, 20 Nov 2026 18:43:19 +0000 [thread overview]
Message-ID: <bug-2153-3@https.bugs.dpdk.org/> (raw)
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@dpdk.org
Reporter: stephen@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.
reply other threads:[~2026-11-20 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-2153-3@https.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox