From: Henry Martin <bsdhenrymartin@gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Henry Martin <bsdhenrymartin@gmail.com>
Subject: [PATCH net] esp: fix out-of-bounds transport-header read after exthdr walk
Date: Fri, 9 Oct 2026 21:52:32 +0800 [thread overview]
Message-ID: <20261009135233.4084239-1-bsdhenrymartin@gmail.com> (raw)
esp6_input_done2() computes the transport header offset with
ipv6_skip_exthdr(), which walks the extension header chain using the
packet's self-reported header lengths without ever comparing the
running offset against skb->len, so it can return an offset past the
end of the packet. esp6_input_done2() then reads the 2-byte source
port at skb->data + offset out of bounds.
esp4's esp_input_done2() has the same class of problem from a
different direction: ihl is taken from the decrypted inner packet and
is not re-validated after esp_remove_trailer() shrank the skb, so the
2-byte source port read at skb_network_header + ihl can land past the
new end of the packet.
Reject the packet with -EINVAL when there is no room for the port at
the computed offset.
This issue was discovered by Tencent CodeBuddy Security.
Fixes: e27cca96cd68 ("xfrm: add espintcp (RFC 8229)")
Signed-off-by: Henry Martin <bsdhenrymartin@gmail.com>
---
net/ipv4/esp4.c | 12 ++++++++++++
net/ipv6/esp6.c | 11 +++++++++++
2 files changed, 23 insertions(+)
diff --git a/net/ipv4/esp4.c b/net/ipv4/esp4.c
index e76db5817e78e..aaff5a2b659db 100644
--- a/net/ipv4/esp4.c
+++ b/net/ipv4/esp4.c
@@ -744,6 +744,18 @@ int esp_input_done2(struct sk_buff *skb, int err)
struct udphdr *uh = (void *)(skb_network_header(skb) + ihl);
__be16 source;
+ /*
+ * ihl is taken from the decrypted inner packet and is not
+ * re-validated after esp_remove_trailer() shrank the skb;
+ * make sure the 2-byte source port we read below is within
+ * the packet.
+ */
+ if (skb_network_offset(skb) + ihl + sizeof(__be16) >
+ skb->len) {
+ err = -EINVAL;
+ goto out;
+ }
+
switch (x->encap->encap_type) {
case TCP_ENCAP_ESPINTCP:
source = th->source;
diff --git a/net/ipv6/esp6.c b/net/ipv6/esp6.c
index b1c9b36f76dc4..89e8cdf5a26b2 100644
--- a/net/ipv6/esp6.c
+++ b/net/ipv6/esp6.c
@@ -782,6 +782,17 @@ int esp6_input_done2(struct sk_buff *skb, int err)
goto out;
}
+ /*
+ * ipv6_skip_exthdr() can advance past the packet end when the
+ * last extension header claims an oversized length; the
+ * transport header below would then be read out of bounds.
+ * Make sure there is room for the 2-byte source port we read.
+ */
+ if (offset + sizeof(__be16) > skb->len) {
+ err = -EINVAL;
+ goto out;
+ }
+
uh = (void *)(skb->data + offset);
th = (void *)(skb->data + offset);
hdr_len += offset;
--
2.43.7
next reply other threads:[~2026-10-09 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 13:52 Henry Martin [this message]
2026-10-09 13:54 ` [PATCH net] esp: fix out-of-bounds transport-header read after exthdr walk netdev-bot+sinfo
2026-10-10 14:32 ` netdev-bot+sashiko
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=20261009135233.4084239-1-bsdhenrymartin@gmail.com \
--to=bsdhenrymartin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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