From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: Joel Fernandes <joel@joelfernandes.org>,
Jakub Kicinski <kuba@kernel.org>, <stable@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>, <linux-hardening@vger.kernel.org>
Subject: Re: [PATCH] kheaders: Use array declaration instead of char
Date: Fri, 3 Mar 2023 16:19:51 +0100 [thread overview]
Message-ID: <89e3ecb6-0e1a-3d86-cb05-cbb034c68dc4@intel.com> (raw)
In-Reply-To: <20230302224946.never.243-kees@kernel.org>
From: Kees Cook <keescook@chromium.org>
Date: Thu, 2 Mar 2023 14:49:50 -0800
> Under CONFIG_FORTIFY_SOURCE, memcpy() will check the size of destination
> and source buffers. Defining kernel_headers_data as "char" would trip
> this check. Since these addresses are treated as byte arrays, define
> them as arrays (as done everywhere else).
Yet another array-as-one-char, I wonder how many are still here...
>
> This was seen with:
>
> $ cat /sys/kernel/kheaders.tar.xz >> /dev/null
>
> detected buffer overflow in memcpy
> kernel BUG at lib/string_helpers.c:1027!
> ...
> RIP: 0010:fortify_panic+0xf/0x20
> [...]
> Call Trace:
> <TASK>
> ikheaders_read+0x45/0x50 [kheaders]
> kernfs_fop_read_iter+0x1a4/0x2f0
> ...
>
> Reported-by: Jakub Kicinski <kuba@kernel.org>
> Link: https://lore.kernel.org/bpf/20230302112130.6e402a98@kernel.org/
> Tested-by: Jakub Kicinski <kuba@kernel.org>
> Fixes: 43d8ce9d65a5 ("Provide in-kernel headers to make extending kernel easier")
> Cc: Joel Fernandes (Google) <joel@joelfernandes.org>
> Cc: stable@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
> ---
> kernel/kheaders.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
[...]
Thanks,
Olek
next prev parent reply other threads:[~2023-03-03 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 22:49 [PATCH] kheaders: Use array declaration instead of char Kees Cook
2023-03-03 3:08 ` Joel Fernandes
2023-03-03 15:19 ` Alexander Lobakin [this message]
2023-03-03 20:36 ` Kees Cook
2023-03-06 10:39 ` Alexander Lobakin
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=89e3ecb6-0e1a-3d86-cb05-cbb034c68dc4@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yamada.masahiro@socionext.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