Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp5902057imb; Fri, 8 Mar 2019 05:07:10 -0800 (PST) X-Google-Smtp-Source: APXvYqzimAponMqnlKE9xroaLcAr87oyKajyxY0TAn6tLY2ugxJ2bL1pDJ5LB/H90HDx7FrZdGpf X-Received: by 2002:a63:618d:: with SMTP id v135mr16553754pgb.238.1552050430760; Fri, 08 Mar 2019 05:07:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1552050430; cv=none; d=google.com; s=arc-20160816; b=mGytqIwgNnthqO+cB3I5kATEI3k4y9IBRDzFmNBY/YHkm7D5N7ws7/cZKRc23VMxOz 1YkBpyi5caoLlEN9/06HA6ErrbiFzBDdJK7ZSNKxG8PIHZ+UzyqihEhGOtAq1l1og7zC NkW5HXLQqpfUE4p7ZsQLb8pz6+gDcMY5BTdfj5Hn0Hwk574n238pvqCAhFrBzD01Neuz TVJCsWe2zokK06mWUbbDBIWFUkUdXRkPChqBd6GA2Rd6JQnYIYsjFrRc2XSy/7lZQ9sA FX7MijnkMosIoX203UOub7jO9ckpmvNDGW2PF86V4m4RH0LjkDLoF9V6hssje+LJuNmN xsNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=nfSV48vTBMuposw0F4kkjCUPRKjRHFe5X6pFIC4pJ0A=; b=z+SF+KuIHqgIqh/mvH4ETp9zbLrYfTooFwdaTo14TiNZRlMsZLpg9Z4wLA9l0Q0AX1 jHFR3GmMDlUcnqNUKabQoXf+SFLIdH0rkHTC/hsciynAFJHnKSUX0BhAjrycs4D47yt1 DtfsK9tmKMJ6bEZtaFWTkGzFLxSjqNIpbpAENVZRcAQu0zoOVTR7EI9tjfpnY8g/moxx bSq65GAsfVfE8svrhCIvV93HxoaQuy4HpltHWhASspe5DrBERNuqZ4k2GccooS48W0Zf Ew/k7+wc03JI1mZDy8C1yynrzF/Ab+Kh8mSNQRQkfvkBP5dn8YnVwR0hIONtr/Yg9vt+ G79g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Upiw88TM; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y16si7077095pll.83.2019.03.08.05.06.54; Fri, 08 Mar 2019 05:07:10 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Upiw88TM; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727567AbfCHMzu (ORCPT + 99 others); Fri, 8 Mar 2019 07:55:50 -0500 Received: from mail.kernel.org ([198.145.29.99]:59928 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726856AbfCHMzr (ORCPT ); Fri, 8 Mar 2019 07:55:47 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 854CE2085A; Fri, 8 Mar 2019 12:55:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1552049747; bh=hNxn9WCouRfMx+ystporDebGJFfUqAt6cQMdd7INodA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Upiw88TM56082aQMUB239xvHhFVOJygbXnUFzz8Iea0Cq8EmuYhASH1cdMZ2k6+N6 mS6zpZXGlX5mYGePNH8ACndZdj8yu8pTMX7AZSp5afZt1ptdgMhqJ2caBCUwEksAs3 kZQWlXgmoPl9649PXTezCMkgq1PsuX4x2E/zF020= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, David Ahern , "David S. Miller" Subject: [PATCH 4.20 51/76] ipv4: Return error for RTA_VIA attribute Date: Fri, 8 Mar 2019 13:50:03 +0100 Message-Id: <20190308124916.616554953@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190308124914.789210760@linuxfoundation.org> References: <20190308124914.789210760@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.20-stable review patch. If anyone has any objections, please let me know. ------------------ From: David Ahern [ Upstream commit b6e9e5df4ecf100f6a10ab2ade8e46d47a4b9779 ] IPv4 currently does not support nexthops outside of the AF_INET family. Specifically, it does not handle RTA_VIA attribute. If it is passed in a route add request, the actual route added only uses the device which is clearly not what the user intended: $ ip ro add 172.16.1.0/24 via inet6 2001:db8:1::1 dev eth0 $ ip ro ls ... 172.16.1.0/24 dev eth0 Catch this and fail the route add: $ ip ro add 172.16.1.0/24 via inet6 2001:db8:1::1 dev eth0 Error: IPv4 does not support RTA_VIA attribute. Fixes: 03c0566542f4c ("mpls: Netlink commands to add, remove, and dump routes") Signed-off-by: David Ahern Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman --- net/ipv4/fib_frontend.c | 4 ++++ 1 file changed, 4 insertions(+) --- a/net/ipv4/fib_frontend.c +++ b/net/ipv4/fib_frontend.c @@ -710,6 +710,10 @@ static int rtm_to_fib_config(struct net case RTA_GATEWAY: cfg->fc_gw = nla_get_be32(attr); break; + case RTA_VIA: + NL_SET_ERR_MSG(extack, "IPv4 does not support RTA_VIA attribute"); + err = -EINVAL; + goto errout; case RTA_PRIORITY: cfg->fc_priority = nla_get_u32(attr); break;