From: Pavel Skripkin <paskripkin@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: syzbot <syzbot+649e339fa6658ee623d3@syzkaller.appspotmail.com>,
coreteam@netfilter.org, davem@davemloft.net,
kadlec@netfilter.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Write in nft_ct_tmpl_put_pcpu
Date: Tue, 10 Aug 2021 00:16:57 +0300 [thread overview]
Message-ID: <2d002841-402c-2bc3-2b33-3e6d1cd14c23@gmail.com> (raw)
In-Reply-To: <20210809203916.GP607@breakpoint.cc>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
On 8/9/21 11:39 PM, Florian Westphal wrote:
> Pavel Skripkin <paskripkin@gmail.com> wrote:
>> I think, there a missing lock in this function:
>>
>> for_each_possible_cpu(cpu) {
>> ct = per_cpu(nft_ct_pcpu_template, cpu);
(*)
>> if (!ct) >> break;
>> nf_ct_put(ct);
>> per_cpu(nft_ct_pcpu_template, cpu) = NULL;
>>
>> }
>>
>> Syzbot hit a UAF in nft_ct_tmpl_put_pcpu() (*), but freed template should be
>> NULL.
>>
>> So I suspect following scenario:
>>
>>
>> CPU0: CPU1:
>> = per_cpu()
>> = per_cpu()
>>
>> nf_ct_put
>> per_cpu = NULL
>> nf_ct_put()
>> * UAF *
Hi, Florian!
>
> Yes and no. The above is fine since pcpu will return different pointers
> for cpu 0 and 1.
>
Dumb question: why per_cpu() will return 2 different pointers for CPU 1
and CPU 0? As I understand for_each_possible_cpu() will iterate over all
CPUs which could ever be enabled. So, we can hit situation when 2
concurrent processes call per_cpu() with same cpu value (*).
> The race is between two different net namespaces that race when
> changing nft_ct_pcpu_template_refcnt.
> This happens since
>
> commit f102d66b335a417d4848da9441f585695a838934
> netfilter: nf_tables: use dedicated mutex to guard transactions
>
> Before this, all transactions were serialized by a global mutex,
> now we only serialize transactions in the same netns.
>
> Its probably best to add
> DEFINE_MUTEX(nft_ct_pcpu_mutex) and then acquire that when we need to
> inc/dec the nft_ct_pcpu_template_refcnt so we can't have two distinct
> cpus hitting a zero refcount.
>
> Would you send a patch for this?
>
Anyway, I think, moving locking a bit higher is good here, let's test
it. I will prepare a patch, if it will pass syzbot testing, thanks!
#syz test
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
With regards,
Pavel Skripkin
[-- Attachment #2: 0001-netfiler-protect-nft_ct_pcpu_template_refcnt-with-mu.patch --]
[-- Type: text/x-patch, Size: 1635 bytes --]
From 616e99fd3ac738b2b5e43c5bc57f6f8cc7a49da0 Mon Sep 17 00:00:00 2001
From: Pavel Skripkin <paskripkin@gmail.com>
Date: Tue, 10 Aug 2021 00:13:38 +0300
Subject: [PATCH] netfiler: protect nft_ct_pcpu_template_refcnt with mutex
/* .... */
Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
---
net/netfilter/nft_ct.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/net/netfilter/nft_ct.c b/net/netfilter/nft_ct.c
index 337e22d8b40b..99b1de14ff7e 100644
--- a/net/netfilter/nft_ct.c
+++ b/net/netfilter/nft_ct.c
@@ -41,6 +41,7 @@ struct nft_ct_helper_obj {
#ifdef CONFIG_NF_CONNTRACK_ZONES
static DEFINE_PER_CPU(struct nf_conn *, nft_ct_pcpu_template);
static unsigned int nft_ct_pcpu_template_refcnt __read_mostly;
+static DEFINE_MUTEX(nft_ct_pcpu_mutex);
#endif
static u64 nft_ct_get_eval_counter(const struct nf_conn_counter *c,
@@ -525,8 +526,10 @@ static void __nft_ct_set_destroy(const struct nft_ctx *ctx, struct nft_ct *priv)
#endif
#ifdef CONFIG_NF_CONNTRACK_ZONES
case NFT_CT_ZONE:
+ mutex_lock(&nft_ct_pcpu_mutex);
if (--nft_ct_pcpu_template_refcnt == 0)
nft_ct_tmpl_put_pcpu();
+ mutex_unlock(&nft_ct_pcpu_mutex);
break;
#endif
default:
@@ -564,9 +567,13 @@ static int nft_ct_set_init(const struct nft_ctx *ctx,
#endif
#ifdef CONFIG_NF_CONNTRACK_ZONES
case NFT_CT_ZONE:
- if (!nft_ct_tmpl_alloc_pcpu())
+ mutex_lock(&nft_ct_pcpu_mutex);
+ if (!nft_ct_tmpl_alloc_pcpu()) {
+ mutex_unlock(&nft_ct_pcpu_mutex);
return -ENOMEM;
+ }
nft_ct_pcpu_template_refcnt++;
+ mutex_unlock(&nft_ct_pcpu_mutex);
len = sizeof(u16);
break;
#endif
--
2.32.0
next prev parent reply other threads:[~2021-08-09 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 13:44 [syzbot] KASAN: use-after-free Write in nft_ct_tmpl_put_pcpu syzbot
2021-08-07 20:50 ` syzbot
2021-08-09 19:22 ` Pavel Skripkin
2021-08-09 20:39 ` Florian Westphal
2021-08-09 21:16 ` Pavel Skripkin [this message]
2021-08-09 21:40 ` Florian Westphal
2021-08-10 3:18 ` syzbot
2021-08-10 2:59 ` syzbot
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=2d002841-402c-2bc3-2b33-3e6d1cd14c23@gmail.com \
--to=paskripkin@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzbot+649e339fa6658ee623d3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).