From: Paolo Abeni <pabeni@redhat.com>
To: "Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] udp_tunnel: avoid calling the wrong GRO handler
Date: Wed, 9 Sep 2026 11:02:24 +0200 [thread overview]
Message-ID: <c64ea248-6c91-4ce9-aacc-b9128dc08b4c@redhat.com> (raw)
In-Reply-To: <20260906211351.1272699-2-Jeremy.Jean@oss.cyber.gouv.fr>
On 9/6/26 11:13 PM, Jérémy Jean wrote:
> setup_udp_tunnel_sock() installs the GRO handlers before updating the
> global static call. The socket is already bound, so packets can arrive
> while the static call still points to the handler for another tunnel
> type. Receive and completion can then parse the packet differently,
> leading to OOB write.
Interesting. A stack trace would be useful. As pointed out by sashiko
the issue is very likely reachable even without the static call.
I wild guess sort of full GRO flush is required before installing or
removing a tunnel, regardless the static call infra.
> Removing the static call is enough since the existing fallback already
> calls the handler selected during setup through call_gro_receive_sk().
> The helper also performs the same recursion check and sets the flush
> flag when the limit is reached.
>
> Fixes: 5d7f5b2f6b93 ("udp_tunnel: use static call for GRO hooks when possible")
> Assisted-by: Codex:gpt-6
Even this one is interesting; this patch left out things that I supposed
much older model should catch easily.
Also please see commit 816d9992d9ed434ec52cfbd63080d518e535a41b
/P
prev parent reply other threads:[~2026-09-09 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 21:13 [PATCH] udp_tunnel: avoid calling the wrong GRO handler Jérémy Jean
2026-09-09 3:16 ` netdev-bot+sashiko
2026-09-09 9:02 ` Paolo Abeni [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=c64ea248-6c91-4ce9-aacc-b9128dc08b4c@redhat.com \
--to=pabeni@redhat.com \
--cc=Jeremy.Jean@oss.cyber.gouv.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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