From: Kees Cook <kees@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
"GONG, Ruiqi" <gongruiqi@huaweicloud.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>, Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Kees Cook <keescook@chromium.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org,
Wang Weiyang <wangweiyang2@huawei.com>,
Xiu Jianfeng <xiujianfeng@huawei.com>,
gongruiqi1@huawei.com
Subject: Re: [PATCH v2] netfilter: ebtables: fix fortify warnings
Date: Tue, 08 Aug 2023 16:00:36 -0700 [thread overview]
Message-ID: <45DEF7A6-093D-4517-8CD8-D86D1671BE48@kernel.org> (raw)
In-Reply-To: <ZNJuMoe37L02TP20@work>
On August 8, 2023 9:32:50 AM PDT, "Gustavo A. R. Silva" <gustavoars@kernel.org> wrote:
>On Tue, Aug 08, 2023 at 09:30:38PM +0800, GONG, Ruiqi wrote:
>> From: "GONG, Ruiqi" <gongruiqi1@huawei.com>
>>
>> When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following
>> warning appears:
>>
>> In function ‘fortify_memcpy_chk’,
>> inlined from ‘size_entry_mwt’ at net/bridge/netfilter/ebtables.c:2118:2:
>> ./include/linux/fortify-string.h:592:25: error: call to ‘__read_overflow2_field’
>> declared with attribute warning: detected read beyond size of field (2nd parameter);
>> maybe use struct_group()? [-Werror=attribute-warning]
>> 592 | __read_overflow2_field(q_size_field, size);
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> The compiler is complaining:
>>
>> memcpy(&offsets[1], &entry->watchers_offset,
>> sizeof(offsets) - sizeof(offsets[0]));
>>
>> where memcpy reads beyong &entry->watchers_offset to copy
>> {watchers,target,next}_offset altogether into offsets[]. Silence the
>> warning by wrapping these three up via struct_group().
>>
>> Signed-off-by: GONG, Ruiqi <gongruiqi1@huawei.com>
>> ---
>>
>> v2: fix HDRTEST error by replacing struct_group() with __struct_group(),
>> since it's a uapi header.
>>
>> include/uapi/linux/netfilter_bridge/ebtables.h | 14 ++++++++------
>> net/bridge/netfilter/ebtables.c | 3 +--
>> 2 files changed, 9 insertions(+), 8 deletions(-)
>>
>> diff --git a/include/uapi/linux/netfilter_bridge/ebtables.h b/include/uapi/linux/netfilter_bridge/ebtables.h
>> index a494cf43a755..b0caad82b693 100644
>> --- a/include/uapi/linux/netfilter_bridge/ebtables.h
>> +++ b/include/uapi/linux/netfilter_bridge/ebtables.h
>> @@ -182,12 +182,14 @@ struct ebt_entry {
>> unsigned char sourcemsk[ETH_ALEN];
>> unsigned char destmac[ETH_ALEN];
>> unsigned char destmsk[ETH_ALEN];
>> - /* sizeof ebt_entry + matches */
>> - unsigned int watchers_offset;
>> - /* sizeof ebt_entry + matches + watchers */
>> - unsigned int target_offset;
>> - /* sizeof ebt_entry + matches + watchers + target */
>> - unsigned int next_offset;
>> + __struct_group(/* no tag */, offsets, /* no attrs */,
>> + /* sizeof ebt_entry + matches */
>> + unsigned int watchers_offset;
>> + /* sizeof ebt_entry + matches + watchers */
>> + unsigned int target_offset;
>> + /* sizeof ebt_entry + matches + watchers + target */
>> + unsigned int next_offset;
>> + );
>> unsigned char elems[0] __attribute__ ((aligned (__alignof__(struct ebt_replace))));
>> };
Actually, looking at what size_entry_mwt() is doing, I think you probably DO want a tag for this and to use a real structure for the manipulations instead of doing array indexing? I dunno. This is a weird function! :)
-Kees
>>
>> diff --git a/net/bridge/netfilter/ebtables.c b/net/bridge/netfilter/ebtables.c
>> index 757ec46fc45a..5ec66b1ebb64 100644
>> --- a/net/bridge/netfilter/ebtables.c
>> +++ b/net/bridge/netfilter/ebtables.c
>> @@ -2115,8 +2115,7 @@ static int size_entry_mwt(const struct ebt_entry *entry, const unsigned char *ba
>> return ret;
>>
>> offsets[0] = sizeof(struct ebt_entry); /* matches come first */
>> - memcpy(&offsets[1], &entry->watchers_offset,
>> - sizeof(offsets) - sizeof(offsets[0]));
>> + memcpy(&offsets[1], &entry->offsets, sizeof(offsets) - sizeof(offsets[0]));
> ^^^^^^^^^^^^
>You now can replace this ____________________________________|
>with just `sizeof(entry->offsets)`
>
>With that change you can add my
>Reviewed-by: Gustavo A. R. Silva <gustavoars@kernel.org>
>
>Thank you
>--
>Gustavo
>
>>
>> if (state->buf_kern_start) {
>> buf_start = state->buf_kern_start + state->buf_kern_offset;
>> --
>> 2.41.0
>>
--
Kees Cook
next prev parent reply other threads:[~2023-08-08 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 13:30 GONG, Ruiqi
2023-08-08 16:32 ` Gustavo A. R. Silva
2023-08-08 22:53 ` Kees Cook
2023-08-09 7:00 ` GONG, Ruiqi
2023-08-09 7:31 ` GONG, Ruiqi
2023-08-08 23:00 ` Kees Cook [this message]
2023-08-09 3:25 ` GONG, Ruiqi
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=45DEF7A6-093D-4517-8CD8-D86D1671BE48@kernel.org \
--to=kees@kernel.org \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=gongruiqi1@huawei.com \
--cc=gongruiqi@huaweicloud.com \
--cc=gustavoars@kernel.org \
--cc=kadlec@netfilter.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=wangweiyang2@huawei.com \
--cc=xiujianfeng@huawei.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®