* [PATCH bpf] bpf: prevent non-ipv4 socket to be added into sock map
@ 2018-05-30 21:28 Wei Wang
0 siblings, 0 replies; only message in thread
From: Wei Wang @ 2018-05-30 21:28 UTC (permalink / raw)
To: netdev, John Fastabend; +Cc: Eric Dumazet, Willem de Bruijn, Wei Wang
From: Wei Wang <weiwan@google.com>
Sock map only supports IPv4 socket proto right now.
If a non-IPv4 socket gets stored in the BPF map, sk->sk_prot gets
overwritten with the v4 tcp prot.
It could potentially cause issues when invoking functions from
sk->sk_prot later in the stack.
Fixes: 174a79ff9515 ("bpf: sockmap with sk redirect support")
Signed-off-by: Wei Wang <weiwan@google.com>
Acked-by: Eric Dumazet <edumazet@google.com>
Acked-by: Willem de Bruijn <willemb@google.com>
---
kernel/bpf/sockmap.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/kernel/bpf/sockmap.c b/kernel/bpf/sockmap.c
index 95a84b2f10ce..1984922f99ee 100644
--- a/kernel/bpf/sockmap.c
+++ b/kernel/bpf/sockmap.c
@@ -1873,6 +1873,11 @@ static int sock_map_update_elem(struct bpf_map *map,
return -EOPNOTSUPP;
}
+ if (skops.sk->sk_family != AF_INET) {
+ fput(socket->file);
+ return -EAFNOSUPPORT;
+ }
+
err = sock_map_ctx_update_elem(&skops, map, key, flags);
fput(socket->file);
return err;
--
2.17.1.1185.g55be947832-goog
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2018-05-30 21:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-30 21:28 [PATCH bpf] bpf: prevent non-ipv4 socket to be added into sock map Wei Wang
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).