From: Jakub Kicinski <kuba@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-hardening@vger.kernel.org, bpf@vger.kernel.org,
"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: Re: splat in ikheaders_read (bpftrace)
Date: Thu, 2 Mar 2023 14:35:27 -0800 [thread overview]
Message-ID: <20230302143527.4bee6f7e@kernel.org> (raw)
In-Reply-To: <20230302141231.2c0a3761@kernel.org>
On Thu, 2 Mar 2023 14:12:31 -0800 Jakub Kicinski wrote:
> On Thu, 2 Mar 2023 14:08:14 -0800 Jakub Kicinski wrote:
> > Mm. Actually stopping to look at the code - I don't see it bound
> > checking against kernel_headers_data_end :| Maybe we need:
> >
> > @@ -34,6 +35,7 @@ ikheaders_read(struct file *file, struct kobject *kobj,
> > struct bin_attribute *bin_attr,
> > char *buf, loff_t off, size_t len)
> > {
> > + len = min_t(size_t, kernel_headers_data_end - kernel_headers_data, len);
> > memcpy(buf, &kernel_headers_data + off, len);
> > return len;
> > }
>
> Scratch that, the size is set at init time.
> My guess was memcpy() thinks the size of kernel_headers_data
> is 1 since it's declared as char?
Like this?
---->8--------------------
From 7549153017144281c2475d9370962ad4d0ea8d4c Mon Sep 17 00:00:00 2001
From: Jakub Kicinski <kuba@kernel.org>
Date: Thu, 2 Mar 2023 11:15:53 -0800
Subject: [PATCH] kheaders: use a flex array for the symbol
Kernels with hardened copy hit:
detected buffer overflow in memcpy
kernel BUG at lib/string_helpers.c:1027!
invalid opcode: 0000 [#8] SMP KASAN
CPU: 1 PID: 1094 Comm: tar Tainted: G D 6.2.0-12879-g040b4d2ce1ad #646
RIP: 0010:fortify_panic+0xf/0x20
[...]
Call Trace:
<TASK>
ikheaders_read+0x45/0x50 [kheaders]
kernfs_fop_read_iter+0x1a4/0x2f0
Repro:
$ cat /sys/kernel/kheaders.tar.xz >> /dev/null
Fixes: 43d8ce9d65a5 ("Provide in-kernel headers to make extending kernel easier")
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
| 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--git a/kernel/kheaders.c b/kernel/kheaders.c
index 8f69772af77b..90562eb4093a 100644
--- a/kernel/kheaders.c
+++ b/kernel/kheaders.c
@@ -26,7 +26,7 @@ asm (
" .popsection \n"
);
-extern char kernel_headers_data;
+extern char kernel_headers_data[];
extern char kernel_headers_data_end;
static ssize_t
@@ -34,7 +34,7 @@ ikheaders_read(struct file *file, struct kobject *kobj,
struct bin_attribute *bin_attr,
char *buf, loff_t off, size_t len)
{
- memcpy(buf, &kernel_headers_data + off, len);
+ memcpy(buf, &kernel_headers_data[off], len);
return len;
}
@@ -49,7 +49,7 @@ static struct bin_attribute kheaders_attr __ro_after_init = {
static int __init ikheaders_init(void)
{
kheaders_attr.size = (&kernel_headers_data_end -
- &kernel_headers_data);
+ &kernel_headers_data[0]);
return sysfs_create_bin_file(kernel_kobj, &kheaders_attr);
}
--
2.39.2
next prev parent reply other threads:[~2023-03-02 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 19:21 splat in ikheaders_read (bpftrace) Jakub Kicinski
2023-03-02 21:57 ` Kees Cook
2023-03-02 22:08 ` Jakub Kicinski
2023-03-02 22:12 ` Jakub Kicinski
2023-03-02 22:35 ` Jakub Kicinski [this message]
2023-03-02 22:39 ` Kees Cook
2023-03-02 22:41 ` Jakub Kicinski
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=20230302143527.4bee6f7e@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=joel@joelfernandes.org \
--cc=kees@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
/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