* Coverity: nf_tables_addchain(): Memory - corruptions
@ 2021-06-08 17:47 coverity-bot
2021-06-08 20:13 ` Florian Westphal
0 siblings, 1 reply; 2+ messages in thread
From: coverity-bot @ 2021-06-08 17:47 UTC (permalink / raw)
To: Florian Westphal; +Cc: Pablo Neira Ayuso, Gustavo A. R. Silva, linux-next
Hello!
This is an experimental semi-automated report about issues detected by
Coverity from a scan of next-20210608 as part of the linux-next scan project:
https://scan.coverity.com/projects/linux-next-weekly-scan
You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by commits:
Mon Jun 7 12:23:38 2021 +0200
7b4b2fa37587 ("netfilter: annotate nf_tables base hook ops")
Coverity reported the following:
*** CID 1505166: Memory - corruptions (UNINIT)
/net/netfilter/nf_tables_api.c: 2188 in nf_tables_addchain()
2182 err = PTR_ERR(trans);
2183 goto err_unregister_hook;
2184 }
2185
2186 nft_trans_chain_policy(trans) = NFT_CHAIN_POLICY_UNSET;
2187 if (nft_is_base_chain(chain)) {
vvv CID 1505166: Memory - corruptions (UNINIT)
vvv Using uninitialized value "basechain".
2188 basechain->ops.hook_ops_type = NF_HOOK_OP_NF_TABLES;
2189 nft_trans_chain_policy(trans) = policy;
2190 }
2191
2192 err = nft_chain_add(table, chain);
2193 if (err < 0) {
If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please
include these lines (but double-check the "Fixes" first):
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Addresses-Coverity-ID: 1505166 ("Memory - corruptions")
Fixes: 7b4b2fa37587 ("netfilter: annotate nf_tables base hook ops")
Thanks for your attention!
--
Coverity-bot
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Coverity: nf_tables_addchain(): Memory - corruptions
2021-06-08 17:47 Coverity: nf_tables_addchain(): Memory - corruptions coverity-bot
@ 2021-06-08 20:13 ` Florian Westphal
0 siblings, 0 replies; 2+ messages in thread
From: Florian Westphal @ 2021-06-08 20:13 UTC (permalink / raw)
To: coverity-bot
Cc: Florian Westphal, Pablo Neira Ayuso, Gustavo A. R. Silva, linux-next
coverity-bot <keescook@chromium.org> wrote:
> 2186 nft_trans_chain_policy(trans) = NFT_CHAIN_POLICY_UNSET;
> 2187 if (nft_is_base_chain(chain)) {
> vvv CID 1505166: Memory - corruptions (UNINIT)
> vvv Using uninitialized value "basechain".
> 2188 basechain->ops.hook_ops_type = NF_HOOK_OP_NF_TABLES;
> 2189 nft_trans_chain_policy(trans) = policy;
Hmm, I do not see how is_base_chain() can be true while basechain
pointer is garbage.
However its probably better for readability to move the NF_HOOK_OP_...
assignment closer to where the basechain ops are allocated.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-06-08 20:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-08 17:47 Coverity: nf_tables_addchain(): Memory - corruptions coverity-bot
2021-06-08 20:13 ` Florian Westphal
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).