From: Florian Westphal <fw@strlen.de>
To: 성병찬 <tjdqudcks0424@naver.com>
Cc: netfilter-devel@vger.kernel.org, pablo@netfilter.org, phil@nwl.cc
Subject: Re: [BUG] netfilter: IPv6 conntrack fragment reassembly truncates header offset
Date: Tue, 29 Sep 2026 09:20:30 +0200 [thread overview]
Message-ID: <artmviCh2h4vYLKG@strlen.de> (raw)
In-Reply-To: <622191c6a9b35335b65fdb07f8914b7@cweb016.nm>
성병찬 <tjdqudcks0424@naver.com> wrote:
> I found a reproducible IPv6 conntrack fragment reassembly bug in:
>
> net/ipv6/netfilter/nf_conntrack_reasm.c
>
> Tested kernel:
>
> Linux v7.2.8
> commit 9a66fdc0d7fd55f54235524a73435af99051e46f
> x86_64 with KASAN enabled
>
> In find_prev_fhdr(), the previous Next Header offset is stored in u8:
>
> u8 prev_nhoff = netoff + offsetof(struct ipv6hdr, nexthdr);
Please send a formal patch, thanks.
next prev parent reply other threads:[~2026-09-29 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 5:34 [BUG] netfilter: IPv6 conntrack fragment reassembly truncates header offset 성병찬
2026-09-29 7:20 ` Florian Westphal [this message]
2026-09-29 9:07 ` Pablo Neira Ayuso
[not found] <31da96413a406da2116f44df2db84f@cweb009.nm>
2026-09-29 9:01 ` Pablo Neira Ayuso
2026-09-29 9:14 ` 성병찬
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=artmviCh2h4vYLKG@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=tjdqudcks0424@naver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox