From: Pavel Machek <pavel@ucw.cz>
To: gregkh@linuxfoundation.org
Cc: dsahern@kernel.org, davem@davemloft.net,
nicolas.dichtel@6wind.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ipv6: Check attribute length for RTA_GATEWAY in multipath" failed to apply to 4.4-stable tree
Date: Sun, 9 Jan 2022 10:30:59 +0100 [thread overview]
Message-ID: <20220109093058.GA8434@amd> (raw)
In-Reply-To: <164156331217042@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
Hi!
> The patch below does not apply to the 4.4-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
I could not find better place to reply.
I see this patch is queued for 5.10 and 4.19. But it is wrong:
> >From 4619bcf91399f00a40885100fb61d594d8454033 Mon Sep 17 00:00:00 2001
> From: David Ahern <dsahern@kernel.org>
> Date: Thu, 30 Dec 2021 17:36:33 -0700
> Subject: [PATCH] ipv6: Check attribute length for RTA_GATEWAY in multipath
> route
>
> Commit referenced in the Fixes tag used nla_memcpy for RTA_GATEWAY as
> does the current nla_get_in6_addr. nla_memcpy protects against accessing
> memory greater than what is in the attribute, but there is no check
> requiring the attribute to have an IPv6 address. Add it.
>
> Fixes: 51ebd3181572 ("ipv6: add support of equal cost multipath
> (ECMP)")
...> @@ -5264,7 +5277,13 @@ static int ip6_route_multipath_add(struct fib6_config *cfg,
>
> nla = nla_find(attrs, attrlen, RTA_GATEWAY);
> if (nla) {
> - r_cfg.fc_gateway = nla_get_in6_addr(nla);
> + int ret;
> +
> + ret = fib6_gw_from_attr(&r_cfg.fc_gateway, nla,
> + extack);
> + if (ret)
> + return ret;
> +
Direct return may not be used here. It needs to goto cleanup.
It is already fixed in mainline, so you can probably just cherry-pick
followup patch, too.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2022-01-09 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 13:48 FAILED: patch "[PATCH] ipv6: Check attribute length for RTA_GATEWAY in multipath" failed to apply to 4.4-stable tree gregkh
2022-01-09 9:30 ` Pavel Machek [this message]
2022-01-09 10:07 ` Greg KH
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=20220109093058.GA8434@amd \
--to=pavel@ucw.cz \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=nicolas.dichtel@6wind.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).