From: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
To: linux-block@vger.kernel.org
Cc: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Subject: [PATCH] blktrace: put bounds on BLKTRACESETUP buf_size and buf_nr
Date: Wed, 3 Jun 2020 22:44:34 -0700 [thread overview]
Message-ID: <20200604054434.216698-1-harshadshirwadkar@gmail.com> (raw)
Make sure that user requested memory via BLKTRACESETUP is within
bounds. This can be easily exploited by setting really large values
for buf_size and buf_nr in BLKTRACESETUP ioctl.
blktrace program has following hardcoded values for bufsize and bufnr:
BUF_SIZE=(512 * 1024)
BUF_NR=(4)
We add buffer to this and define the upper bound to be as follows:
BUF_SIZE=(1024 * 1024)
BUF_NR=(16)
This is very easy to exploit. Setting buf_size / buf_nr in userspace
program to big values make kernel go oom. Verified that the fix makes
BLKTRACESETUP return -E2BIG if the buf_size * buf_nr crosses the upper
bound.
Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
---
include/uapi/linux/blktrace_api.h | 3 +++
kernel/trace/blktrace.c | 3 +++
2 files changed, 6 insertions(+)
diff --git a/include/uapi/linux/blktrace_api.h b/include/uapi/linux/blktrace_api.h
index 690621b610e5..4d9dc44a83f9 100644
--- a/include/uapi/linux/blktrace_api.h
+++ b/include/uapi/linux/blktrace_api.h
@@ -129,6 +129,9 @@ enum {
};
#define BLKTRACE_BDEV_SIZE 32
+#define BLKTRACE_MAX_BUFSIZ (1024 * 1024)
+#define BLKTRACE_MAX_BUFNR 16
+#define BLKTRACE_MAX_ALLOC ((BLKTRACE_MAX_BUFNR) * (BLKTRACE_MAX_BUFNR))
/*
* User setup structure passed with BLKTRACESETUP
diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
index ea47f2084087..b3b0a8164c05 100644
--- a/kernel/trace/blktrace.c
+++ b/kernel/trace/blktrace.c
@@ -482,6 +482,9 @@ static int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
if (!buts->buf_size || !buts->buf_nr)
return -EINVAL;
+ if (buts->buf_size * buts->buf_nr > BLKTRACE_MAX_ALLOC)
+ return -E2BIG;
+
if (!blk_debugfs_root)
return -ENOENT;
--
2.27.0.rc2.251.g90737beb825-goog
next reply other threads:[~2020-06-04 5:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 5:44 Harshad Shirwadkar [this message]
2020-06-04 7:10 ` [PATCH] blktrace: put bounds on BLKTRACESETUP buf_size and buf_nr Chaitanya Kulkarni
2020-06-04 15:26 ` harshad shirwadkar
2020-06-05 4:31 ` Bart Van Assche
2020-06-05 5:02 ` harshad shirwadkar
2020-06-05 13:43 ` Bart Van Assche
2020-06-05 17:39 ` harshad shirwadkar
2020-06-08 6:42 ` Chaitanya Kulkarni
2020-06-08 6:40 ` Chaitanya Kulkarni
2020-06-08 14:20 ` Bart Van Assche
2020-06-08 21:59 ` Chaitanya Kulkarni
2020-06-08 23:40 ` harshad shirwadkar
2020-06-09 0:00 ` Chaitanya Kulkarni
2020-06-08 6:34 ` Chaitanya Kulkarni
2020-06-08 14:13 ` Bart Van Assche
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=20200604054434.216698-1-harshadshirwadkar@gmail.com \
--to=harshadshirwadkar@gmail.com \
--cc=linux-block@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