From: patchwork-bot+netdevbpf@kernel.org
To: Chris Arges <carges@cloudflare.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, dsahern@kernel.org,
idosch@nvidia.com, june@cloudflare.com, danjones@cloudflare.com,
jbrandeburg@cloudflare.com, josef@toxicpanda.com,
mason@kernel.org, kernel-team@cloudflare.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH] net: prevent receive header offset overflow during decapsulation
Date: Thu, 19 Nov 2026 14:40:05 +0000 [thread overview]
Message-ID: <179509920504.3130597.3198388033732007048.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261118-prevent_rx_header_offset_overflow-v1-1-92a5be55f994@cloudflare.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 18 Nov 2026 08:32:27 -0600 you wrote:
> Repeated decapsulation can leave skb->data far from skb->head while
> the remaining packet data is still valid. Since the skb header positions
> are 16-bit offsets, a later header update can truncate and make header
> access use unrelated bytes and eventually crash.
>
> Limit receive headroom to 32 KiB. This is well beyond the headroom of
> normal packets while allowing the networking stack to pull enough
> headers in a single pass without overflowing 16-bit header offsets.
>
> [...]
Here is the summary with links:
- net: prevent receive header offset overflow during decapsulation
https://git.kernel.org/netdev/net/c/b10c986f1769
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-19 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 14:32 [PATCH] net: prevent receive header offset overflow during decapsulation Chris J Arges
2026-11-18 14:38 ` netdev-bot+sinfo
2026-11-18 17:39 ` netdev-bot+sashiko
2026-11-19 1:40 ` Chris Arges
2026-11-19 14:15 ` Ido Schimmel
2026-11-19 14:40 ` patchwork-bot+netdevbpf [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=179509920504.3130597.3198388033732007048.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=carges@cloudflare.com \
--cc=danjones@cloudflare.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jbrandeburg@cloudflare.com \
--cc=josef@toxicpanda.com \
--cc=june@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@kernel.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 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.