From: Jerome Forissier <jerome.forissier@arm.com>
To: u-boot@lists.u-boot-project.org, Esteban Alba <estebancalba@gmail.com>
Cc: trini@konsulko.com, rfried.dev@gmail.com,
v.v.mitrofanov@yadro.com, sjg@chromium.org, nd <nd@arm.com>
Subject: Re: [PATCH v2] net: net6: validate IPv6 payload and transport lengths on receive
Date: Fri, 11 Sep 2026 15:18:07 +0200 [thread overview]
Message-ID: <7cd8cef6-81f2-4f07-8357-60b768fbf0cd@arm.com> (raw)
In-Reply-To: <20260821-net6-len-validation-v2-1-29bd39f946e0@gmail.com>
On Fri, 21 Aug 2026 02:07:43 -0500, Esteban Alba wrote:
> net_ip6_handler() checks the received length only against IP6_HDR_SIZE and
> then uses length fields from the packet without checking them. The checksum
> is computed over payload_len, but the UDP handler length comes from
> udp_len. A sender can keep payload_len correct so the checksum still
> validates and set udp_len larger than the frame. A handler that trusts that
> length then reads or writes past the receive buffer. The DHCPv6 client
> copies the declared number of bytes and can be made to write past the
> packet buffer from a single link-local ADVERTISE.
>
> [...]
Applied to u-boot-net branch for-main, thanks!
[1/1] net: net6: validate IPv6 payload and transport lengths on receive
commit: 80215cdacd2acfe92152344e5269461446aa80ff
Best regards,
--
Jerome Forissier <jerome.forissier@arm.com>
prev parent reply other threads:[~2026-09-11 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 2:09 [PATCH] net: net6: validate IPv6 payload and UDP length on receive Esteban Alba
2026-08-08 2:09 ` Esteban Alba via B4 Relay
2026-08-14 8:05 ` Jerome Forissier
2026-08-21 7:07 ` [PATCH v2] net: net6: validate IPv6 payload and transport lengths " Esteban Alba
2026-08-21 7:07 ` Esteban Alba via B4 Relay
2026-09-03 9:23 ` Jerome Forissier
2026-09-11 13:18 ` Jerome Forissier [this message]
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=7cd8cef6-81f2-4f07-8357-60b768fbf0cd@arm.com \
--to=jerome.forissier@arm.com \
--cc=estebancalba@gmail.com \
--cc=nd@arm.com \
--cc=rfried.dev@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
--cc=v.v.mitrofanov@yadro.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.