From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+5d8c5789c8cb076b2c25@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfilter?] KASAN: slab-use-after-free Read in nf_tables_trans_destroy_work (2)
Date: Mon, 3 Mar 2025 19:30:12 +0800 [thread overview]
Message-ID: <20250303113013.2959-1-hdanton@sina.com> (raw)
In-Reply-To: <67c447a7.050a0220.55417.04d3.GAE@google.com>
On Sun, 02 Mar 2025 03:57:27 -0800
> syzbot found the following issue on:
>
> HEAD commit: 03d38806a902 Merge tag 'thermal-6.14-rc5' of git://git.ker..
> git tree: upstream
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155128b7980000
#syz test
--- x/include/net/netfilter/nf_tables.h
+++ y/include/net/netfilter/nf_tables.h
@@ -1915,6 +1915,7 @@ struct nftables_pernet {
unsigned int base_seq;
unsigned int gc_seq;
u8 validate_state;
+ u8 flushed;
};
extern unsigned int nf_tables_net_id;
--- x/net/netfilter/nf_tables_api.c
+++ y/net/netfilter/nf_tables_api.c
@@ -10654,6 +10654,9 @@ static int nf_tables_commit(struct net *
mutex_unlock(&nft_net->commit_mutex);
return 0;
}
+ if (nft_net->flushed) {
+ return -EAGAIN;
+ }
nft_ctx_init(&ctx, net, skb, nlh, NFPROTO_UNSPEC, NULL, NULL, NULL);
@@ -11251,6 +11254,7 @@ static int nf_tables_abort(struct net *n
else
nf_tables_module_autoload_cleanup(net);
+ nft_net->flushed = 0;
mutex_unlock(&nft_net->commit_mutex);
return ret;
@@ -11854,6 +11858,7 @@ static int nft_rcv_nl_event(struct notif
gc_seq = nft_gc_seq_begin(nft_net);
nf_tables_trans_destroy_flush_work();
+ nft_net->flushed = 1;
again:
list_for_each_entry(table, &nft_net->tables, list) {
if (nft_table_has_owner(table) &&
@@ -11903,6 +11908,7 @@ static int __net_init nf_tables_init_net
nft_net->base_seq = 1;
nft_net->gc_seq = 0;
nft_net->validate_state = NFT_VALIDATE_SKIP;
+ nft_net->flushed = 0;
return 0;
}
--
next prev parent reply other threads:[~2025-03-03 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 11:57 syzbot
2025-03-03 10:54 ` Hillf Danton
2025-03-03 11:09 ` syzbot
2025-03-03 11:30 ` Hillf Danton [this message]
2025-03-03 11:50 ` syzbot
2025-03-04 3:53 ` [syzbot] KASAN: slab-use-after-free Read in nf_tables_trans_destroy_work syzbot
[not found] <Z8Z5T76R9Y0HhOZ7@strlen.de>
2025-03-04 4:14 ` [syzbot] [netfilter?] KASAN: slab-use-after-free Read in nf_tables_trans_destroy_work (2) 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=20250303113013.2959-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+5d8c5789c8cb076b2c25@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
all inboxes | Powered by JetHome®