From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Cc: "Claude Opus 4.6 \(1M context\)" <noreply@anthropic.com>
Subject: [PATCH 0/3] net: dhcp: fix buffer overflows
Date: Thu, 02 Apr 2026 08:56:28 +0200 [thread overview]
Message-ID: <20260402-net-dhcp-buffer-overflows-v1-0-cd60b651a629@pengutronix.de> (raw)
Fix buffer overflows on malicious incoming network packets or user data
in the dhcp code.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (3):
net: dhcp: add bounds checking to DHCP option parsing
net: dhcp: use strnlen/xstrndup for bp_file to prevent read past field
net: dhcp: cap DHCP option string length to 255 bytes
net/dhcp.c | 36 +++++++++++++++++++++++++-----------
1 file changed, 25 insertions(+), 11 deletions(-)
---
base-commit: 0933e8f2ebf0d91dfcf177a4e4292b02921a53f1
change-id: 20260402-net-dhcp-buffer-overflows-94a0e80363c1
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2026-04-02 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 6:56 Sascha Hauer [this message]
2026-04-02 6:56 ` [PATCH 1/3] net: dhcp: add bounds checking to DHCP option parsing Sascha Hauer
2026-04-02 6:56 ` [PATCH 2/3] net: dhcp: use strnlen/xstrndup for bp_file to prevent read past field Sascha Hauer
2026-04-02 6:56 ` [PATCH 3/3] net: dhcp: cap DHCP option string length to 255 bytes Sascha Hauer
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=20260402-net-dhcp-buffer-overflows-v1-0-cd60b651a629@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=noreply@anthropic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox