linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] net: bpf: reject invalid shifts
Date: Tue, 12 Jan 2016 18:55:07 +0100	[thread overview]
Message-ID: <1452621307-2213-1-git-send-email-rabin@rab.in> (raw)

On ARM64, a BUG() is triggered in the eBPF JIT if a filter with a
constant shift that can't be encoded in the immediate field of the
UBFM/SBFM instructions is passed to the JIT.  Since these shifts
amounts, which are negative or >= regsize, are invalid, reject then in
the eBPF verifier and the classic BPF filter checker, for all
architectures.

Signed-off-by: Rabin Vincent <rabin@rab.in>
---
 kernel/bpf/verifier.c | 10 ++++++++++
 net/core/filter.c     |  5 +++++
 2 files changed, 15 insertions(+)

diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index a7945d10b378..3643df0dfaa9 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -1121,6 +1121,16 @@ static int check_alu_op(struct verifier_env *env, struct bpf_insn *insn)
 			return -EINVAL;
 		}
 
+		if ((opcode == BPF_LSH || opcode == BPF_RSH) &&
+		    BPF_SRC(insn->code) == BPF_K) {
+			int size = BPF_CLASS(insn->code) == BPF_ALU64 ? 64 : 32;
+
+			if (insn->imm < 0 || insn->imm >= size) {
+				verbose("invalid shift %d\n", insn->imm);
+				return -EINVAL;
+			}
+		}
+
 		/* pattern match 'bpf_add Rx, imm' instruction */
 		if (opcode == BPF_ADD && BPF_CLASS(insn->code) == BPF_ALU64 &&
 		    regs[insn->dst_reg].type == FRAME_PTR &&
diff --git a/net/core/filter.c b/net/core/filter.c
index 672eefbfbe99..37157c4c1a78 100644
--- a/net/core/filter.c
+++ b/net/core/filter.c
@@ -777,6 +777,11 @@ static int bpf_check_classic(const struct sock_filter *filter,
 			if (ftest->k == 0)
 				return -EINVAL;
 			break;
+		case BPF_ALU | BPF_LSH | BPF_K:
+		case BPF_ALU | BPF_RSH | BPF_K:
+			if (ftest->k >= 32)
+				return -EINVAL;
+			break;
 		case BPF_LD | BPF_MEM:
 		case BPF_LDX | BPF_MEM:
 		case BPF_ST:
-- 
2.6.4

             reply	other threads:[~2016-01-12 17:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 17:55 Rabin Vincent [this message]
2016-01-12 18:51 ` [PATCH] net: bpf: reject invalid shifts Alexei Starovoitov
2016-01-12 19:17   ` [PATCHv2] " Rabin Vincent
2016-01-12 19:26     ` Alexei Starovoitov
2016-01-12 19:35     ` Daniel Borkmann
2016-01-12 19:48     ` Eric Dumazet
2016-01-12 19:53       ` Alexei Starovoitov
2016-01-12 20:42         ` Daniel Borkmann
2016-01-12 20:46           ` Alexei Starovoitov
2016-01-12 23:28             ` Eric Dumazet
2016-01-12 23:47               ` Alexei Starovoitov
2016-01-12 23:59                 ` Hannes Frederic Sowa
2016-01-13  0:17                   ` Hannes Frederic Sowa
2016-01-13  0:19                   ` Alexei Starovoitov
2016-01-13  0:42                     ` Hannes Frederic Sowa
2016-01-13  2:11                 ` Eric Dumazet
2016-01-13  2:24                   ` Alexei Starovoitov
2016-01-13  2:45                     ` David Miller
2016-01-13  2:43                   ` David Miller
2016-01-13  4:07                     ` Eric Dumazet
2016-01-13  5:00                       ` David Miller
2016-01-13  4:27                     ` Hannes Frederic Sowa
2016-01-12 22:34         ` Eric Dumazet
2016-01-12 20:56     ` David Miller

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=1452621307-2213-1-git-send-email-rabin@rab.in \
    --to=rabin@rab.in \
    --cc=linux-arm-kernel@lists.infradead.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).