From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Daniel Borkmann <borkmann@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: netdev@vger.kernel.org, Jesper Dangaard Brouer <brouer@redhat.com>
Subject: [RFC net-next PATCH 2/2] bpf: disallow XDP data_meta to overlap with xdp_frame area
Date: Wed, 18 Apr 2018 14:10:16 +0200 [thread overview]
Message-ID: <152405341684.30730.9208803786283211244.stgit@firesoul> (raw)
In-Reply-To: <152405338404.30730.9846848505925123326.stgit@firesoul>
If combining xdp_adjust_head and xdp_adjust_meta, then it is possible
to make data_meta overlap with area used by xdp_frame. And another
invocation of xdp_adjust_head can then clear that area, due to
clearing of xdp_frame area.
The easiest solution I found was to simply not allow
xdp_buff->data_meta to overlap with area used by xdp_frame.
Fixes: 6dfb970d3dbd ("xdp: avoid leaking info stored in frame data on page reuse")
Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
---
net/core/filter.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/net/core/filter.c b/net/core/filter.c
index 15e9b5477360..e3623e741181 100644
--- a/net/core/filter.c
+++ b/net/core/filter.c
@@ -2701,6 +2701,11 @@ BPF_CALL_2(bpf_xdp_adjust_head, struct xdp_buff *, xdp, int, offset)
data > xdp->data_end - ETH_HLEN))
return -EINVAL;
+ /* Disallow data_meta to use xdp_frame area */
+ if (metalen > 0 &&
+ unlikely((data - metalen) < xdp_frame_end))
+ return -EINVAL;
+
/* Avoid info leak, when reusing area prev used by xdp_frame */
if (data < xdp_frame_end) {
unsigned long clearlen = xdp_frame_end - data;
@@ -2734,6 +2739,7 @@ static const struct bpf_func_proto bpf_xdp_adjust_head_proto = {
BPF_CALL_2(bpf_xdp_adjust_meta, struct xdp_buff *, xdp, int, offset)
{
+ void *xdp_frame_end = xdp->data_hard_start + sizeof(struct xdp_frame);
void *meta = xdp->data_meta + offset;
unsigned long metalen = xdp->data - meta;
@@ -2742,6 +2748,11 @@ BPF_CALL_2(bpf_xdp_adjust_meta, struct xdp_buff *, xdp, int, offset)
if (unlikely(meta < xdp->data_hard_start ||
meta > xdp->data))
return -EINVAL;
+
+ /* Disallow data_meta to use xdp_frame area */
+ if (unlikely(meta < xdp_frame_end))
+ return -EINVAL;
+
if (unlikely((metalen & (sizeof(__u32) - 1)) ||
(metalen > 32)))
return -EACCES;
next prev parent reply other threads:[~2018-04-18 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 12:10 [RFC net-next PATCH 0/2] bpf: followup avoid leaking info stored in frame data on page reuse Jesper Dangaard Brouer
2018-04-18 12:10 ` [RFC net-next PATCH 1/2] bpf: avoid clear xdp_frame area again Jesper Dangaard Brouer
2018-04-18 12:10 ` Jesper Dangaard Brouer [this message]
2018-04-18 16:21 ` [RFC net-next PATCH 2/2] bpf: disallow XDP data_meta to overlap with xdp_frame area Daniel Borkmann
2018-04-18 17:53 ` Jesper Dangaard Brouer
2018-04-18 20:28 ` 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=152405341684.30730.9208803786283211244.stgit@firesoul \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=borkmann@iogearbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox