From: Helen Koike <koike@igalia.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: fw@strlen.de, phil@nwl.cc, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-dev@igalia.com
Subject: Re: [PATCH] netfilter: nf_tables: fix use-after-free on ops->dev
Date: Tue, 3 Mar 2026 11:33:04 -0300 [thread overview]
Message-ID: <17499d82-ad03-44a9-ab3a-429d2ebea02f@igalia.com> (raw)
In-Reply-To: <aaYYiPTO5JYOlhhY@chamomile>
Hi Pablo,
Thanks for your quick reply, please see my comments below.
On 3/2/26 8:08 PM, Pablo Neira Ayuso wrote:
> On Mon, Mar 02, 2026 at 06:26:05PM -0300, Helen Koike wrote:
>> struct nf_hook_ops has a pointer to dev, which can be used by
>> __nf_unregister_net_hook() after it has been freed by tun_chr_close().
>>
>> Fix it by calling dev_hold() when saving dev to ops struct.
>
> Sorry, I don't think this patch works, dev_hold()/dev_put() use
> per_cpu area.
In my understanding, being a percpu_ref shouldn't affect the behavior,
since after a percpu_ref_kill() it switches to the usual mode with
shared atomic_t counter.
But if I understood correctly from your comment below, the proper
solution would be to fix the order that the hooks are released, is my
understanding correct?
>
> The nf_tables_flowtable_event() function used to release the hook, but
> now things have changed since there is auto-hook registration.
I'll investigate this further. Thanks a lot for the pointer (and sorry
for the noise).
Regards,
Helen
>
>> Reported-by: syzbot+bb9127e278fa198e110c@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=bb9127e278fa198e110c
>> Signed-off-by: Helen Koike <koike@igalia.com>
>> ---
>> net/netfilter/nf_tables_api.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
>> index fd7f7e4e2a43..00b5f900a51d 100644
>> --- a/net/netfilter/nf_tables_api.c
>> +++ b/net/netfilter/nf_tables_api.c
>> @@ -352,6 +352,7 @@ static void nft_netdev_hook_free_ops(struct nft_hook *hook)
>>
>> list_for_each_entry_safe(ops, next, &hook->ops_list, list) {
>> list_del(&ops->list);
>> + dev_put(ops->dev);
>> kfree(ops);
>> }
>> }
>> @@ -2374,6 +2375,7 @@ static struct nft_hook *nft_netdev_hook_alloc(struct net *net,
>> err = -ENOMEM;
>> goto err_hook_free;
>> }
>> + dev_hold(dev);
>> ops->dev = dev;
>> list_add_tail(&ops->list, &hook->ops_list);
>> }
>> --
>> 2.53.0
>>
next prev parent reply other threads:[~2026-03-03 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 21:26 Helen Koike
2026-03-02 23:08 ` Pablo Neira Ayuso
2026-03-03 14:33 ` Helen Koike [this message]
2026-03-04 5:32 ` Florian Westphal
2026-03-04 12:26 ` Phil Sutter
2026-03-04 13:38 ` Florian Westphal
2026-03-04 14:59 ` Helen Koike
2026-03-04 12:49 ` Phil Sutter
2026-03-04 13:28 ` 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=17499d82-ad03-44a9-ab3a-429d2ebea02f@igalia.com \
--to=koike@igalia.com \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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®