From: Ryan Prinz <rc4d5a@protonmail.com>
To: netdev-bot+sashiko@kernel.org
Cc: Alexander Aring <alex.aring@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Simon Horman <horms@kernel.org>, Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, linux-wpan@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Ryan Prinz <rc4d5a@protonmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>
Subject: Re: [PATCH net RESEND] ieee802154: 6lowpan: validate fragment offset against datagram size
Date: Thu, 12 Nov 2026 15:29:59 +0000 [thread overview]
Message-ID: <20261112152819.1014850-1-rc4d5a@protonmail.com> (raw)
In-Reply-To: <179447431152.2199510.14609873818368730049@kernel.org>
Thanks for the review! These are fair points, I'll respin.
- The accepted offset range has a closed upper bound (offset + length
== d_size is allowed, as needed for the final fragment, including a
zero-length one at offset == d_size), not the open [0, d_size) I
described.
- 802.15.4 has no source authentication without llsec, so this bug
doesn't let an attacker impersonate another sender as the message
implied. The real effect is an attacker's fragment getting spliced
into the reassembled datagram in place of a legitimate sender's
bytes for a given span, via the overlap-eviction path you described.
- The CVE-2019-8359/Contiki-NG comparison doesn't match. That was an
out-of-bounds write into a fixed buffer. This is a reassembly
data-integrity issue only, since inet_frag_reasm_finish() links skbs
by pointer rather than copying into a computed offset. Dropping that
comparison.
Sending v2 with the commit message corrected; the fix itself is
unchanged.
pw-bot: cr
next prev parent reply other threads:[~2026-11-12 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 22:32 [PATCH] " Ryan Prinz
2026-11-08 13:05 ` [PATCH RESEND] " Ryan Prinz
2026-11-08 14:20 ` [PATCH net " Ryan Prinz
2026-11-09 9:03 ` Ryan Prinz
2026-11-12 9:05 ` netdev-bot+sashiko
2026-11-12 15:29 ` Ryan Prinz [this message]
2026-11-12 15:31 ` [PATCH net v2] " Ryan Prinz
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=20261112152819.1014850-1-rc4d5a@protonmail.com \
--to=rc4d5a@protonmail.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.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
all inboxes | Powered by JetHome®