netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: conntrack: fix rmmod double-free race
Date: Tue, 14 Feb 2023 13:53:07 +0100	[thread overview]
Message-ID: <Y+uEM5Rmr5ARRoKz@salvia> (raw)
In-Reply-To: <20230213175737.26685-1-fw@strlen.de>

On Mon, Feb 13, 2023 at 06:57:37PM +0100, Florian Westphal wrote:
> nf_conntrack_hash_check_insert() callers free the ct entry directly, via
> nf_conntrack_free.
> 
> This isn't allowed anymore in all cases: Its possible that
> nf_conntrack_hash_check_insert() placed the entry into the conntrack
> table and then found that a conntrack extension has been removed at the
> same time.
> 
> In this case, the just-added entry is removed again and an error is
> returned to the caller.
> 
> Problem is that another cpu might have picked up this entry and
> incremented its reference count.
> 
> This results in a use-after-free/double-free, once by the other cpu and
> once by the caller of nf_conntrack_hash_check_insert().
> 
> Fix this by making nf_conntrack_hash_check_insert() always set a
> refcount.
> 
> Refcount is set to 2 right before insertion, so we only need to make
> sure we set it to 1 in all error branches that can occur before
> inserting the enry into the hash.
> 
> Callers can then just call nf_ct_put(), which will also take care of
> ct->master reference.
> 
> While at it, make the function return -EAGAIN in the rmmod (genid
> changed) case, this makes nfnetlink replay the command (suggested
> by Pablo Neira).
> 
> Fixes: c56716c69ce1 ("netfilter: extensions: introduce extension genid count")
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
>  This is on top of
>  "net: netfilter: fix possible refcount leak in ctnetlink_create_conntrack()"
> 
>  net/netfilter/nf_conntrack_bpf.c     |  3 +--
>  net/netfilter/nf_conntrack_core.c    | 11 +++++++----
>  net/netfilter/nf_conntrack_netlink.c |  8 +++-----
>  3 files changed, 11 insertions(+), 11 deletions(-)
> 
> diff --git a/net/netfilter/nf_conntrack_bpf.c b/net/netfilter/nf_conntrack_bpf.c
> index 24002bc61e07..9de5a32088d2 100644
> --- a/net/netfilter/nf_conntrack_bpf.c
> +++ b/net/netfilter/nf_conntrack_bpf.c
> @@ -381,10 +381,9 @@ struct nf_conn *bpf_ct_insert_entry(struct nf_conn___init *nfct_i)
>  	struct nf_conn *nfct = (struct nf_conn *)nfct_i;
>  	int err;
>  
> -	nfct->status |= IPS_CONFIRMED;
>  	err = nf_conntrack_hash_check_insert(nfct);
>  	if (err < 0) {
> -		nf_conntrack_free(nfct);
> +		nf_ct_put(nfct);
>  		return NULL;
>  	}
>  	return nfct;
> diff --git a/net/netfilter/nf_conntrack_core.c b/net/netfilter/nf_conntrack_core.c
> index 496c4920505b..2eeb2e2b8e46 100644
> --- a/net/netfilter/nf_conntrack_core.c
> +++ b/net/netfilter/nf_conntrack_core.c
> @@ -887,8 +887,9 @@ nf_conntrack_hash_check_insert(struct nf_conn *ct)
>  	zone = nf_ct_zone(ct);
>  
>  	if (!nf_ct_ext_valid_pre(ct->ext)) {
> -		NF_CT_STAT_INC_ATOMIC(net, insert_failed);
> -		return -ETIMEDOUT;
> +		/* so caller can use nf_ct_put() */
> +		refcount_set(&ct->ct_general.use, 1);
> +		return -EAGAIN;
>  	}
>  
>  	local_bh_disable();
> @@ -924,6 +925,7 @@ nf_conntrack_hash_check_insert(struct nf_conn *ct)
>  			goto chaintoolong;
>  	}
>  
> +	ct->status |= IPS_CONFIRMED;
>  	smp_wmb();
>  	/* The caller holds a reference to this object */
>  	refcount_set(&ct->ct_general.use, 2);
> @@ -934,8 +936,7 @@ nf_conntrack_hash_check_insert(struct nf_conn *ct)
>  
>  	if (!nf_ct_ext_valid_post(ct->ext)) {
>  		nf_ct_kill(ct);

I think this nf_ct_kill() delivers a destroy to userspace for an entry
that was never added?

lock is not held anymore, so maybe a packet already got this
conntrack.

Maybe post validation also needs to hold the lock and
nf_conntrack_hash_check_insert() could undo the list insertion itself
leaving things as they were before calling this function?

> -		NF_CT_STAT_INC_ATOMIC(net, drop);
> -		return -ETIMEDOUT;
> +		return -EAGAIN;
>  	}
>  
>  	return 0;
> @@ -943,6 +944,8 @@ nf_conntrack_hash_check_insert(struct nf_conn *ct)
>  	NF_CT_STAT_INC(net, chaintoolong);
>  	err = -ENOSPC;
>  out:
> +	/* so caller can use nf_ct_put() */
> +	refcount_set(&ct->ct_general.use, 1);
>  	nf_conntrack_double_unlock(hash, reply_hash);
>  	local_bh_enable();
>  	return err;
> diff --git a/net/netfilter/nf_conntrack_netlink.c b/net/netfilter/nf_conntrack_netlink.c
> index ca4d5bb1ea52..dc448c5bc3f1 100644
> --- a/net/netfilter/nf_conntrack_netlink.c
> +++ b/net/netfilter/nf_conntrack_netlink.c
> @@ -2316,9 +2316,6 @@ ctnetlink_create_conntrack(struct net *net,
>  	nfct_seqadj_ext_add(ct);
>  	nfct_synproxy_ext_add(ct);
>  
> -	/* we must add conntrack extensions before confirmation. */
> -	ct->status |= IPS_CONFIRMED;
> -
>  	if (cda[CTA_STATUS]) {
>  		err = ctnetlink_change_status(ct, cda);
>  		if (err < 0)
> @@ -2382,8 +2379,9 @@ ctnetlink_create_conntrack(struct net *net,
>  	return ct;
>  
>  err3:
> -	if (ct->master)
> -		nf_ct_put(ct->master);
> +	rcu_read_unlock();
> +	nf_ct_put(ct);

I can see your intention is to consolidate all around nf_ct_put(), but
I wonder if it would be better if nf_conntrack_hash_check_insert()
handles error by removing the entry from the list.

> +	return ERR_PTR(err);
>  err2:
>  	rcu_read_unlock();
>  err1:
> -- 
> 2.39.1
> 

  reply	other threads:[~2023-02-14 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 17:57 [PATCH nf] netfilter: conntrack: fix rmmod double-free race Florian Westphal
2023-02-14 12:53 ` Pablo Neira Ayuso [this message]
2023-02-14 15:48   ` Florian Westphal

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=Y+uEM5Rmr5ARRoKz@salvia \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).