diff options
author | Florian Westphal <fw@strlen.de> | 2023-05-04 14:55:02 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-05-24 17:32:32 +0100 |
commit | d9176dc690bcb9bd45b1ac088f372d6eaa8aa6c9 (patch) | |
tree | a488d395e84436346d0a17d359e26d5431465a70 /include | |
parent | 30e4b13b1bfbdf3bf3b27036d8209ea1b9f0d880 (diff) | |
download | linux-stable-d9176dc690bcb9bd45b1ac088f372d6eaa8aa6c9.tar.gz linux-stable-d9176dc690bcb9bd45b1ac088f372d6eaa8aa6c9.tar.bz2 linux-stable-d9176dc690bcb9bd45b1ac088f372d6eaa8aa6c9.zip |
netfilter: conntrack: fix possible bug_on with enable_hooks=1
[ Upstream commit e72eeab542dbf4f544e389e64fa13b82a1b6d003 ]
I received a bug report (no reproducer so far) where we trip over
712 rcu_read_lock();
713 ct_hook = rcu_dereference(nf_ct_hook);
714 BUG_ON(ct_hook == NULL); // here
In nf_conntrack_destroy().
First turn this BUG_ON into a WARN. I think it was triggered
via enable_hooks=1 flag.
When this flag is turned on, the conntrack hooks are registered
before nf_ct_hook pointer gets assigned.
This opens a short window where packets enter the conntrack machinery,
can have skb->_nfct set up and a subsequent kfree_skb might occur
before nf_ct_hook is set.
Call nf_conntrack_init_end() to set nf_ct_hook before we register the
pernet ops.
Fixes: ba3fbe663635 ("netfilter: nf_conntrack: provide modparam to always register conntrack hooks")
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions