From: patchwork-bot+netdevbpf@kernel.org
To: Jean-Paul Sergent <jpsergent@gmail.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
i.maximets@ovn.org, sashal@kernel.org, kuba@kernel.org,
davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
horms@kernel.org, sridhar.samudrala@intel.com, kees@kernel.org
Subject: Re: [PATCH net v3] net: dst_metadata: fix memcmp overread in skb_metadata_dst_cmp
Date: Thu, 12 Nov 2026 12:30:04 +0000 [thread overview]
Message-ID: <179448660448.2065860.8508505178205062232.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109082410.206140-1-jpsergent@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 9 Nov 2026 00:24:10 -0800 you wrote:
> Commit 3fcece12bc1b6 ("net: store port/representator id in
> metadata_dst") dropped the options_len equality check when converting
> skb_metadata_dst_cmp() to a type switch, so the memcmp length is taken
> from skb a alone. When skb b carries fewer options than a, the
> comparison reads past b's allocation.
>
> Hit in practice with Cilium geneve GRO aggregation, comparing an skb
> carrying 12 bytes of tunnel options against one carrying none:
>
> [...]
Here is the summary with links:
- [net,v3] net: dst_metadata: fix memcmp overread in skb_metadata_dst_cmp
https://git.kernel.org/netdev/net/c/74a7db839308
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-12 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 8:24 [PATCH net v3] net: dst_metadata: fix memcmp overread in skb_metadata_dst_cmp Jean-Paul Sergent
2026-11-12 12:30 ` 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=179448660448.2065860.8508505178205062232.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=jpsergent@gmail.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox