[ Upstream commit 90f62cf30a78721641e08737bda787552428061e ]
It is possible by passing a netlink socket to a more privileged
executable and then to fool that executable into writing to the socket
data that happens to be valid netlink message to do something that
privileged executable did not intend to do.
To keep this from happening replace bare capable and ns_capable calls
with netlink_capable, netlink_net_calls and netlink_ns_capable calls.
Which act the same as the previous calls except they verify that the
opener of the socket had the desired permissions as well.
Reported-by: Andy Lutomirski <firstname.lastname@example.org>
Signed-off-by: "Eric W. Biederman" <email@example.com>
Signed-off-by: David S. Miller <firstname.lastname@example.org>
Signed-off-by: Greg Kroah-Hartman <email@example.com>