From: Florian Westphal <fw@strlen.de>
To: Guanglei Zhu <zhugl3@xiaopeng.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Phil Sutter <phil@nwl.cc>,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
liuwb@xiaopeng.com
Subject: Re: [PATCH] netfilter: nf_conntrack_h323: fix NULL deref in decode_seqof()
Date: Mon, 12 Oct 2026 11:12:03 +0200 [thread overview]
Message-ID: <asykY-liuKbPCdwK@strlen.de> (raw)
In-Reply-To: <20261012090835.920932-1-zhugl3@xiaopeng.com>
Guanglei Zhu <zhugl3@xiaopeng.com> wrote:
> decode_seqof() loads son from f->fields and dereferences son->attr
> in the item loop without a NULL check. A number of SEQOF entries
> in nf_conntrack_h323_types.c carry a NULL fields pointer, so a
> crafted packet that makes one of these optional fields present with
> a nonzero item count dereferences NULL in the loop.
>
> Skip the decoding when fields is NULL.
>
> Signed-off-by: Guanglei Zhu <zhugl3@xiaopeng.com>
> ---
> Verified on a KASAN kernel with a test module calling decode_seqof()
> with a fields=NULL SEQOF entry and a nonzero item count: NULL deref
> report at son->attr (read of size 2 at address 0x4).
We don't add NULL tests unless there is a sensibe reason.
Will you add NULL tests to other functions too because a 3rd party
module would crash otherwise?
If this is reachable, show how.
> diff --git a/net/netfilter/nf_conntrack_h323_asn1.c b/net/netfilter/nf_conntrack_h323_asn1.c
> index 6830c9da3..0d07d0276 100644
> --- a/net/netfilter/nf_conntrack_h323_asn1.c
> +++ b/net/netfilter/nf_conntrack_h323_asn1.c
> @@ -691,6 +691,8 @@ static int decode_seqof(struct bitstr *bs, const struct field_t *f,
> }
>
> /* Decode nested field */
> + if (!f->fields)
> + return H323_ERROR_NONE;
> son = f->fields;
This is strange.
son = f->fields;
if (!son)...
would be more natural.
next prev parent reply other threads:[~2026-10-12 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 9:08 Guanglei Zhu
2026-10-12 9:12 ` Florian Westphal [this message]
2026-10-12 9:20 ` Guanglei Zhu
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=asykY-liuKbPCdwK@strlen.de \
--to=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwb@xiaopeng.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=zhugl3@xiaopeng.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
all inboxes | Powered by JetHome®