From: Daniel Borkmann <daniel@iogearbox.net>
To: ast@kernel.org
Cc: jannh@google.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf 7/9] bpf: fix check_map_access smin_value test when pointer contains offset
Date: Tue, 1 Jan 2019 21:49:23 +0100 [thread overview]
Message-ID: <20190101204925.4584-8-daniel@iogearbox.net> (raw)
In-Reply-To: <20190101204925.4584-1-daniel@iogearbox.net>
In check_map_access() we probe actual bounds through __check_map_access()
with offset of reg->smin_value + off for lower bound and offset of
reg->umax_value + off for the upper bound. However, even though the
reg->smin_value could have a negative value, the final result of the
sum with off could be positive when pointer arithmetic with known and
unknown scalars is combined. In this case we reject the program with
an error such as "R<x> min value is negative, either use unsigned index
or do a if (index >=0) check." even though the access itself would be
fine. Therefore extend the check to probe whether the actual resulting
reg->smin_value + off is less than zero.
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Alexei Starovoitov <ast@kernel.org>
---
kernel/bpf/verifier.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index eebbc03..8e5da1c 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -1443,13 +1443,17 @@ static int check_map_access(struct bpf_verifier_env *env, u32 regno,
*/
if (env->log.level)
print_verifier_state(env, state);
+
/* The minimum value is only important with signed
* comparisons where we can't assume the floor of a
* value is 0. If we are using signed variables for our
* index'es we need to make sure that whatever we use
* will have a set floor within our range.
*/
- if (reg->smin_value < 0) {
+ if (reg->smin_value < 0 &&
+ (reg->smin_value == S64_MIN ||
+ (off + reg->smin_value != (s64)(s32)(off + reg->smin_value)) ||
+ reg->smin_value + off < 0)) {
verbose(env, "R%d min value is negative, either use unsigned index or do a if (index >=0) check.\n",
regno);
return -EACCES;
--
2.9.5
next prev parent reply other threads:[~2019-01-01 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 20:49 [PATCH bpf 0/9] bpf fix to prevent oob under speculation Daniel Borkmann
2019-01-01 20:49 ` [PATCH bpf 1/9] bpf: move {prev_,}insn_idx into verifier env Daniel Borkmann
2019-01-01 20:49 ` [PATCH bpf 2/9] bpf: move tmp variable into ax register in interpreter Daniel Borkmann
2019-01-01 20:49 ` [PATCH bpf 3/9] bpf: enable access to ax register also from verifier rewrite Daniel Borkmann
2019-01-01 21:17 ` David Miller
2019-01-01 20:49 ` [PATCH bpf 4/9] bpf: restrict map value pointer arithmetic for unpriviledged Daniel Borkmann
2019-01-01 20:49 ` [PATCH bpf 5/9] bpf: restrict stack " Daniel Borkmann
2019-01-01 21:20 ` David Miller
2019-01-01 22:57 ` Daniel Borkmann
2019-01-01 20:49 ` [PATCH bpf 6/9] bpf: restrict unknown scalars of mixed signed bounds " Daniel Borkmann
2019-01-01 20:49 ` Daniel Borkmann [this message]
2019-01-01 20:49 ` [PATCH bpf 8/9] bpf: prevent out of bounds speculation on pointer arithmetic Daniel Borkmann
2019-01-01 20:49 ` [PATCH bpf 9/9] bpf: add various test cases to selftests Daniel Borkmann
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=20190101204925.4584-8-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=jannh@google.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).