All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: Alexei Starovoitov <ast@plumgrid.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net] net: filter: initialize A and X registers
Date: Wed, 23 Apr 2014 09:53:37 +0200	[thread overview]
Message-ID: <53577181.1000406@redhat.com> (raw)
In-Reply-To: <1398223137-5463-1-git-send-email-ast@plumgrid.com>

On 04/23/2014 05:18 AM, Alexei Starovoitov wrote:
> exisiting BPF verifier allows uninitialized access to registers,
> 'ret A' is considered to be a valid filter.
> So initialize A and X to zero to prevent leaking kernel memory
> In the future BPF verifier will be rejecting such filters
>
> Signed-off-by: Alexei Starovoitov <ast@plumgrid.com>
> Cc: Daniel Borkmann <dborkman@redhat.com>

I gave it some more thought, it's actually more than just 'ret A'
from your description, user programs could be used to generate code
like 'add X' or 'add #42' instead of a txa or load instruction [where
A is previously uninitialized], as it was always initialized to 0
before. We prevent to do a 'ret X', but X could be uninitialized and
then transferred over to taint A etc. So yeah, this patch is the most
simple way to prevent that w/o huge complexity. Therefore, it's
better this way:

Acked-by: Daniel Borkmann <dborkman@redhat.com>

  parent reply	other threads:[~2014-04-23  7:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  3:18 [PATCH net] net: filter: initialize A and X registers Alexei Starovoitov
2014-04-23  3:57 ` David Miller
2014-04-23  4:59   ` Alexei Starovoitov
2014-04-23  7:02     ` Daniel Borkmann
2014-04-23 16:52       ` David Miller
2014-04-23 17:20         ` Daniel Borkmann
2014-04-23 16:50     ` David Miller
2014-04-23 20:38       ` Alexei Starovoitov
2014-04-23 21:39         ` Eric Dumazet
2014-04-23 22:19           ` Alexei Starovoitov
2014-04-24  2:55             ` Eric Dumazet
2014-04-24  3:22               ` Alexei Starovoitov
2014-04-25  8:23                 ` Daniel Borkmann
2014-04-24  7:07               ` Martin Schwidefsky
2014-04-23  5:13   ` Eric Dumazet
2014-04-23 11:45     ` Daniel Borkmann
2014-04-23 13:39       ` Eric Dumazet
2014-04-23 21:07         ` David Miller
2014-04-23 16:51     ` David Miller
2014-04-23 17:10       ` Daniel Borkmann
2014-04-23 17:14       ` Eric Dumazet
2014-04-24 17:24         ` David Miller
2014-04-24 18:11           ` Eric Dumazet
2014-04-24 22:18           ` Daniel Borkmann
2014-04-23  7:53 ` Daniel Borkmann [this message]
2014-04-23 16:13   ` Alexei Starovoitov
2014-04-23 19:35 ` 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=53577181.1000406@redhat.com \
    --to=dborkman@redhat.com \
    --cc=ast@plumgrid.com \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.