From: Steffen Klassert <steffen.klassert@secunet.com>
To: Ren Wei <weir@nebusec.ai>
Cc: <netdev@vger.kernel.org>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <horms@kernel.org>, <sd@queasysnail.net>,
<vega@nebusec.ai>, <wf.kernel.dev@gmail.com>
Subject: Re: [PATCH net 1/1] net: xfrm: reject unrepresentable espintcp transport headers
Date: Thu, 3 Sep 2026 09:38:45 +0200 [thread overview]
Message-ID: <apkkBfCh9BdOzGEZ@secunet.com> (raw)
In-Reply-To: <d138815e0f52e8898e83c5db62b3938993f813a2.1787986691.git.wf.kernel.dev@gmail.com>
On Sat, Aug 29, 2026 at 11:44:32PM +0800, Ren Wei wrote:
> From: Wyatt Feng <wf.kernel.dev@gmail.com>
>
> ESP-in-TCP can hand xfrm packets whose transport header offset no longer
> fits after the stream parser trims the TCP envelope. The plain transport
> header reset truncates that offset and triggers the skb warning path.
>
> Use the careful transport-header helper and drop the skb through the
> existing XFRM error path when the offset cannot be represented.
>
> Fixes: e27cca96cd68 ("xfrm: add espintcp (RFC 8229)")
> Cc: stable@vger.kernel.org
> Reported-by: Vega <vega@nebusec.ai>
> Assisted-by: Codex:GPT-5.4
> Signed-off-by: Wyatt Feng <wf.kernel.dev@gmail.com>
> Signed-off-by: Ren Wei <weir@nebusec.ai>
Applied, thanks a lot!
prev parent reply other threads:[~2026-09-03 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 15:44 [PATCH net 0/1] net: xfrm: espintcp can trip skb transport-header warning Ren Wei
2026-08-29 15:44 ` [PATCH net 1/1] net: xfrm: reject unrepresentable espintcp transport headers Ren Wei
2026-09-03 7:38 ` Steffen Klassert [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=apkkBfCh9BdOzGEZ@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=vega@nebusec.ai \
--cc=weir@nebusec.ai \
--cc=wf.kernel.dev@gmail.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.