From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: dsahern@gmail.com, stable@vger.kernel.org, mfadon@teldat.com
Subject: Re: [PATCH] vrf: Fix use after free and double free in vrf_finish_output
Date: Wed, 11 Apr 2018 19:50:42 +0200 [thread overview]
Message-ID: <20180411175042.GA21729@kroah.com> (raw)
In-Reply-To: <20180411.111254.899190774974818612.davem@davemloft.net>
On Wed, Apr 11, 2018 at 11:12:54AM -0400, David Miller wrote:
> From: David Ahern <dsahern@gmail.com>
> Date: Wed, 11 Apr 2018 08:10:03 -0700
>
> > [ upstream commit 82dd0d2a9a76fc8fa2b18d80b987d455728bf83a ]
> >
> > Miguel reported an skb use after free / double free in vrf_finish_output
> > when neigh_output returns an error. The vrf driver should return after
> > the call to neigh_output as it takes over the skb on error path as well.
> >
> > Patch is a simplified version of Miguel's patch which was written for 4.9,
> > and updated to top of tree.
> >
> > Fixes: 8f58336d3f78a ("net: Add ethernet header for pass through VRF device")
> > Signed-off-by: Miguel Fadon Perlines <mfadon@teldat.com>
> > Signed-off-by: David Ahern <dsahern@gmail.com>
> > Signed-off-by: David S. Miller <davem@davemloft.net>
> > [ backport to 4.4 and 4.9 dropped the sock_confirm_neigh and
> > changed neigh_output to dst_neigh_output ]
> > ---
> > note to stable: this patch applies to both 4.9 and 4.4 (the latter
> > has an offset but still applies cleanly
>
> Stable folks, please queue this up.
Now applied, thanks!
greg k-h
prev parent reply other threads:[~2018-04-11 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 8:34 FAILED: patch "[PATCH] vrf: Fix use after free and double free in vrf_finish_output" failed to apply to 4.9-stable tree gregkh
2018-04-11 15:10 ` [PATCH] vrf: Fix use after free and double free in vrf_finish_output David Ahern
2018-04-11 15:12 ` David Miller
2018-04-11 17:50 ` Greg KH [this message]
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=20180411175042.GA21729@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=mfadon@teldat.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).