All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: fgao@ikuai8.com
Cc: netfilter-devel@vger.kernel.org, gfree.wind@gmail.com
Subject: Re: [PATCH v7 nf] netfilter: synproxy: Check oom when adding synproxy and seqadj ct extensions
Date: Mon, 12 Sep 2016 19:15:09 +0200	[thread overview]
Message-ID: <20160912171509.GA28913@salvia> (raw)
In-Reply-To: <1473432621-20908-1-git-send-email-fgao@ikuai8.com>

On Fri, Sep 09, 2016 at 10:50:21PM +0800, fgao@ikuai8.com wrote:
> From: Gao Feng <fgao@ikuai8.com>
> 
> When memory is exhausted, nfct_seqadj_ext_add may fail to add the
> synproxy and seqadj extensions. The function nf_ct_seqadj_init doesn't
> check if get valid seqadj pointer by the nfct_seqadj.
> 
> Now drop the packet directly when fail to add seqadj extension to
> avoid dereference NULL pointer in nf_ct_seqadj_init from
> init_conntrack().
> 
> Signed-off-by: Gao Feng <fgao@ikuai8.com>
> ---
>  v7: Remove one debug log and revert to NF_DROP again;
>  v6: Add one helper function to add synproxy
>  v5: Return NF_ACCEPT instead of NF_DROP when nfct_seqadj_ext_add failed in nf_nat_setup_info
>  v4: Drop the packet directly when fail to add seqadj extension;
>  v3: Remove the warning log when seqadj is null;
>  v2: Remove the unnessary seqadj check in nf_ct_seq_adjust
>  v1: Initial patch
> 
>  include/net/netfilter/nf_conntrack_synproxy.h | 13 +++++++++++++
>  net/netfilter/nf_conntrack_core.c             |  6 +++---
>  net/netfilter/nf_nat_core.c                   |  3 ++-
>  3 files changed, 18 insertions(+), 4 deletions(-)
> 
> diff --git a/include/net/netfilter/nf_conntrack_synproxy.h b/include/net/netfilter/nf_conntrack_synproxy.h
> index 6793614..e8cf825 100644
> --- a/include/net/netfilter/nf_conntrack_synproxy.h
> +++ b/include/net/netfilter/nf_conntrack_synproxy.h
> @@ -27,6 +27,19 @@ static inline struct nf_conn_synproxy *nfct_synproxy_ext_add(struct nf_conn *ct)
>  #endif
>  }
>  
> +static inline bool nf_ct_add_synproxy(struct nf_conn *ct, const struct nf_conn *tmpl)
> +{
> +	if (tmpl && nfct_synproxy(tmpl)) {
> +		if (!nfct_seqadj_ext_add(ct))
> +			return false;
> +
> +		if (!nfct_synproxy_ext_add(ct))
> +			return false;
> +	}
> +
> +	return true;
> +}
> +
>  struct synproxy_stats {
>  	unsigned int			syn_received;
>  	unsigned int			cookie_invalid;
> diff --git a/net/netfilter/nf_conntrack_core.c b/net/netfilter/nf_conntrack_core.c
> index dd2c43a..64aabeb 100644
> --- a/net/netfilter/nf_conntrack_core.c
> +++ b/net/netfilter/nf_conntrack_core.c
> @@ -1035,9 +1035,9 @@ init_conntrack(struct net *net, struct nf_conn *tmpl,
>  	if (IS_ERR(ct))
>  		return (struct nf_conntrack_tuple_hash *)ct;
>  
> -	if (tmpl && nfct_synproxy(tmpl)) {
> -		nfct_seqadj_ext_add(ct);
> -		nfct_synproxy_ext_add(ct);
> +	if (!nf_ct_add_synproxy(ct, tmpl)) {
> +		nf_conntrack_free(ct);
> +		return NULL;

This has to be ERR_PTR(-ENOMEM);

So the packet is dropped.

NULL is used for invalid packets, invalid packets keep going and the
user can drop them via -m state --state INVALID.

      reply	other threads:[~2016-09-12 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 14:50 [PATCH v7 nf] netfilter: synproxy: Check oom when adding synproxy and seqadj ct extensions fgao
2016-09-12 17:15 ` Pablo Neira Ayuso [this message]

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=20160912171509.GA28913@salvia \
    --to=pablo@netfilter.org \
    --cc=fgao@ikuai8.com \
    --cc=gfree.wind@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.