From: Kees Cook <keescook@chromium.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Kees Cook <kees@kernel.org>,
linux-hardening@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: splat in ikheaders_read (bpftrace)
Date: Thu, 2 Mar 2023 14:39:17 -0800 [thread overview]
Message-ID: <64012596.170a0220.1940.0a34@mx.google.com> (raw)
In-Reply-To: <20230302141231.2c0a3761@kernel.org>
On Thu, Mar 02, 2023 at 02:12:31PM -0800, Jakub Kicinski wrote:
> On Thu, 2 Mar 2023 14:08:14 -0800 Jakub Kicinski wrote:
> > > static ssize_t
> > > 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);
> > > return len;
> > > }
> > >
> > > I will take a look at the caller's allocation of "buf" and kernel_headers_data.
> >
> > 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?
I've improved the reporting, and yeah, it's due to the declaration:
memcpy: detected buffer overflow: 4096 byte read from buffer of size 1
But that's an easy fix -- this has been done in lots of other places. It
needs to be an array, not a single char. (I'm surprised we hadn't seen
this before.)
diff --git a/kernel/kheaders.c b/kernel/kheaders.c
index 8f69772af77b..42163c9e94e5 100644
--- a/kernel/kheaders.c
+++ b/kernel/kheaders.c
@@ -26,15 +26,15 @@ asm (
" .popsection \n"
);
-extern char kernel_headers_data;
-extern char kernel_headers_data_end;
+extern char kernel_headers_data[];
+extern char kernel_headers_data_end[];
static ssize_t
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;
}
@@ -48,8 +48,8 @@ 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);
+ kheaders_attr.size = (kernel_headers_data_end -
+ kernel_headers_data);
return sysfs_create_bin_file(kernel_kobj, &kheaders_attr);
}
--
Kees Cook
next prev parent reply other threads:[~2023-03-02 22:39 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
2023-03-02 22:39 ` Kees Cook [this message]
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=64012596.170a0220.1940.0a34@mx.google.com \
--to=keescook@chromium.org \
--cc=bpf@vger.kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.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