From: Jerome Forissier <jerome.forissier@arm.com>
To: Sean Edmond <seanedmond@microsoft.com>,
Ramon Fried <rfried.dev@gmail.com>,
u-boot@lists.u-boot-project.org,
Shahriyar Jalayeri <shahriyar@byteray.co.uk>
Cc: Argus <argus@byteray.co.uk>, Tom Rini <trini@konsulko.com>,
Francois Berder <fberder@outlook.fr>, nd <nd@arm.com>
Subject: Re: [PATCH 2/2] test: dm: eth: add DHCPv6 oversized option regression tests
Date: Thu, 13 Aug 2026 15:21:46 +0200 [thread overview]
Message-ID: <b9e0f77d-ef28-4a20-a0fb-ff35ee51fefe@arm.com> (raw)
In-Reply-To: <20260806-b4-dhcp6-serverid-oob-v1-2-4ec6857682e1@byteray.co.uk>
On Thu, 06 Aug 2026 20:37:51 +0200, Shahriyar Jalayeri wrote:
> Answer a DHCPv6 SOLICIT from the sandbox eth tx handler with an
> ADVERTISE that carries an option longer than a valid DUID, and check
> the client rejects it rather than sending a REQUEST.
>
> Two cases cover the option parser: an over-long SERVERID, which a client
> that trusts the length copies out of bounds while building the REQUEST,
> and an over-long CLIENTID, which drives a memcmp past the client DUID
> buffer.
>
> [...]
Applied to u-boot-net branch for-main, thanks!
[2/2] test: dm: eth: add DHCPv6 oversized option regression tests
(no commit info)
Best regards,
--
Jerome Forissier <jerome.forissier@arm.com>
next prev parent reply other threads:[~2026-08-13 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 18:37 [PATCH 0/2] net: dhcp6: fix out-of-bounds access in the option parser Shahriyar Jalayeri
2026-08-06 18:37 ` [PATCH 1/2] net: dhcp6: bound received DUID option lengths Shahriyar Jalayeri
2026-08-06 18:37 ` [PATCH 2/2] test: dm: eth: add DHCPv6 oversized option regression tests Shahriyar Jalayeri
2026-08-13 13:21 ` Jerome Forissier [this message]
2026-08-14 15:42 ` [PATCH 0/2] net: dhcp6: fix out-of-bounds access in the option parser Jerome Forissier
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=b9e0f77d-ef28-4a20-a0fb-ff35ee51fefe@arm.com \
--to=jerome.forissier@arm.com \
--cc=argus@byteray.co.uk \
--cc=fberder@outlook.fr \
--cc=nd@arm.com \
--cc=rfried.dev@gmail.com \
--cc=seanedmond@microsoft.com \
--cc=shahriyar@byteray.co.uk \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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