From: Fernando Fernandez Mancera <fmancera@suse.de>
To: Yizhou Zhao <zhaoyz24@mails.tsinghua.edu.cn>,
netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
stable@vger.kernel.org,
Yuxiang Yang <yangyx22@mails.tsinghua.edu.cn>,
Xuewei Feng <fengxw06@126.com>, Qi Li <qli01@tsinghua.edu.cn>,
Ke Xu <xuke@tsinghua.edu.cn>
Subject: Re: [PATCH nft] netfilter: nft_inner: Fix IPv6 inner_thoff desync
Date: Mon, 11 May 2026 14:39:08 +0200 [thread overview]
Message-ID: <0bbeadd4-a4b4-44e9-9312-85e563f2bd1c@suse.de> (raw)
In-Reply-To: <20260510131953.32790-1-zhaoyz24@mails.tsinghua.edu.cn>
On 5/10/26 3:19 PM, Yizhou Zhao wrote:
> In nft_inner_parse_l2l3(), when processing inner IPv6 packets, ipv6_find_hdr()
> correctly computes the transport header offset traversing all extension headers,
> but the result is immediately overwritten with nhoff + sizeof(_ip6h) (40 bytes),
> which only accounts for the IPv6 base header. This creates a desync between
> inner_thoff (wrong — points to extension header start) and l4proto (correct
> — e.g., IPPROTO_TCP), enabling transport header forgery and potential firewall
> bypass. This issue was found and reproduced with the assistance of GLM 5.1 from
> Z.ai, and exists up to Linux 7.1, affecting stable versions from Linux 6.2.
>
I don't think there is need to mention the model here. Please use the
Assisted-by tag instead.
> File: net/netfilter/nft_inner.c
> Function: nft_inner_parse_l2l3()
>
> ```c
> thoff = nhoff;
> l4proto = ipv6_find_hdr(pkt->skb, &thoff, -1, &fragoff, &fh_flags);
> if (l4proto < 0 || thoff > U16_MAX)
> return -1;
> if (fragoff == 0) {
> thoff = nhoff + sizeof(_ip6h); // BUG: overwrites correct thoff
> ctx->inner_thoff = thoff; // stores WRONG offset
> ctx->l4proto = l4proto;
> }
> ```
>
I do not think this is relevant in the commit message.
> For comparison, the normal (non-inner) IPv6 path correctly preserves
> ipv6_find_hdr()'s result. Removing the incorrect overwrite ensures
> that ipv6_find_hdr()’s calculated transport header offset is preserved,
> thereby fixing the desynchronization.
>
The solution makes sense to me. Thanks!
> Fixes: 3a07327d10a09 ("netfilter: nft_inner: support for inner tunnel header matching")
Please stick to a 12 characters long commit hash. Make sure that
checkpatch.pl script passes.
> Reported-by: Yizhou Zhao <zhaoyz24@mails.tsinghua.edu.cn>
> Reported-by: Yuxiang Yang <yangyx22@mails.tsinghua.edu.cn>
> Reported-by: Xuewei Feng <fengxw06@126.com>
> Reported-by: Qi Li <qli01@tsinghua.edu.cn>
> Reported-by: Ke Xu <xuke@tsinghua.edu.cn>
> Reported-by: GLM 5.1 from Z.ai
This isn't correct. It should be Assisted-by tag instead.
Thanks,
Fernando.
> Signed-off-by: Yizhou Zhao <zhaoyz24@mails.tsinghua.edu.cn>
> ---
> net/netfilter/nft_inner.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/net/netfilter/nft_inner.c b/net/netfilter/nft_inner.c
> index c4569d4b9..1b3e7a976 100644
> --- a/net/netfilter/nft_inner.c
> +++ b/net/netfilter/nft_inner.c
> @@ -163,7 +163,6 @@ static int nft_inner_parse_l2l3(const struct nft_inner *priv,
> return -1;
>
> if (fragoff == 0) {
> - thoff = nhoff + sizeof(_ip6h);
> ctx->flags |= NFT_PAYLOAD_CTX_INNER_TH;
> ctx->inner_thoff = thoff;
> ctx->l4proto = l4proto;
next prev parent reply other threads:[~2026-05-11 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 13:19 [PATCH nft] netfilter: nft_inner: Fix IPv6 inner_thoff desync Yizhou Zhao
2026-05-11 12:39 ` Fernando Fernandez Mancera [this message]
2026-05-11 13:37 ` [PATCH v2 " Yizhou Zhao
2026-05-11 16:27 ` Fernando Fernandez Mancera
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=0bbeadd4-a4b4-44e9-9312-85e563f2bd1c@suse.de \
--to=fmancera@suse.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fengxw06@126.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=qli01@tsinghua.edu.cn \
--cc=stable@vger.kernel.org \
--cc=xuke@tsinghua.edu.cn \
--cc=yangyx22@mails.tsinghua.edu.cn \
--cc=zhaoyz24@mails.tsinghua.edu.cn \
/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