From: Fernando Fernandez Mancera <fmancera@suse.de>
To: Xiang Mei <xmei5@asu.edu>, netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
coreteam@netfilter.org, Weiming Shi <bestswngs@gmail.com>
Subject: Re: [PATCH nf v2] netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO
Date: Wed, 15 Apr 2026 10:19:16 +0200 [thread overview]
Message-ID: <767aa4eb-fd87-4bc5-a4ea-654b28310cfb@suse.de> (raw)
In-Reply-To: <20260414221401.2809350-1-xmei5@asu.edu>
On 4/15/26 12:14 AM, Xiang Mei wrote:
> nf_osf_match_one() computes ctx->window % f->wss.val in the
> OSF_WSS_MODULO branch with no guard for f->wss.val == 0. A
> CAP_NET_ADMIN user can add such a fingerprint via nfnetlink; a
> subsequent matching TCP SYN divides by zero and panics the kernel.
>
> Reject the bogus fingerprint in nfnl_osf_add_callback() above the
> per-option for-loop. f->wss is per-fingerprint, not per-option, so
> the check must run regardless of f->opt_num (including 0). Also
> reject wss.wc >= OSF_WSS_MAX; nf_osf_match_one() already treats that
> as "should not happen".
>
> Crash:
> Oops: divide error: 0000 [#1] SMP KASAN NOPTI
> RIP: 0010:nf_osf_match_one (net/netfilter/nfnetlink_osf.c:98)
> Call Trace:
> <IRQ>
> nf_osf_match (net/netfilter/nfnetlink_osf.c:220)
> xt_osf_match_packet (net/netfilter/xt_osf.c:32)
> ipt_do_table (net/ipv4/netfilter/ip_tables.c:348)
> nf_hook_slow (net/netfilter/core.c:622)
> ip_local_deliver (net/ipv4/ip_input.c:265)
> ip_rcv (include/linux/skbuff.h:1162)
> __netif_receive_skb_one_core (net/core/dev.c:6181)
> process_backlog (net/core/dev.c:6642)
> __napi_poll (net/core/dev.c:7710)
> net_rx_action (net/core/dev.c:7945)
> handle_softirqs (kernel/softirq.c:622)
>
> Fixes: 11eeef41d5f6 ("netfilter: passive OS fingerprint xtables match")
> Reported-by: Weiming Shi <bestswngs@gmail.com>
> Suggested-by: Florian Westphal <fw@strlen.de>
> Suggested-by: Pablo Neira Ayuso <pablo@netfilter.org>
> Signed-off-by: Xiang Mei <xmei5@asu.edu>
> ---
This looks good to me.
Reviewed-by: Fernando Fernandez Mancera <fmancera@suse.de>
> v2: Fix the bug in configure path and correct the fix tag
>
> net/netfilter/nfnetlink_osf.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/net/netfilter/nfnetlink_osf.c b/net/netfilter/nfnetlink_osf.c
> index 45d9ad231..70172ca07 100644
> --- a/net/netfilter/nfnetlink_osf.c
> +++ b/net/netfilter/nfnetlink_osf.c
> @@ -320,6 +320,10 @@ static int nfnl_osf_add_callback(struct sk_buff *skb,
> if (f->opt_num > ARRAY_SIZE(f->opt))
> return -EINVAL;
>
> + if (f->wss.wc >= OSF_WSS_MAX ||
> + (f->wss.wc == OSF_WSS_MODULO && f->wss.val == 0))
> + return -EINVAL;
> +
> for (i = 0; i < f->opt_num; i++) {
> if (!f->opt[i].length || f->opt[i].length > MAX_IPOPTLEN)
> return -EINVAL;
next prev parent reply other threads:[~2026-04-15 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 22:14 [PATCH nf v2] netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO Xiang Mei
2026-04-15 8:19 ` Fernando Fernandez Mancera [this message]
2026-04-15 9:29 ` Pablo Neira Ayuso
2026-04-15 9:55 ` Pablo Neira Ayuso
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=767aa4eb-fd87-4bc5-a4ea-654b28310cfb@suse.de \
--to=fmancera@suse.de \
--cc=bestswngs@gmail.com \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=xmei5@asu.edu \
/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