mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tadeusz Struk <tadeusz.struk@linaro.org>
Cc: linux-kernel@vger.kernel.org, sec@valis.email,
	steffen.klassert@secunet.com, stable-commits@vger.kernel.org
Subject: Re: Patch "esp: Fix possible buffer overflow in ESP transformation" has been added to the 4.19-stable tree
Date: Mon, 21 Mar 2022 16:53:37 +0100	[thread overview]
Message-ID: <YjifgTsDes+hiKq6@kroah.com> (raw)
In-Reply-To: <97b7e9f3-8ec3-b824-1301-9cea0a4d3437@linaro.org>

On Mon, Mar 21, 2022 at 07:47:20AM -0700, Tadeusz Struk wrote:
> On 3/21/22 06:12, Greg KH wrote:
> > On Mon, Mar 21, 2022 at 01:37:08PM +0100, gregkh@linuxfoundation.org wrote:
> > > 
> > > This is a note to let you know that I've just added the patch titled
> > > 
> > >      esp: Fix possible buffer overflow in ESP transformation
> > > 
> > > to the 4.19-stable tree which can be found at:
> > >      http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > > 
> > > The filename of the patch is:
> > >       esp-fix-possible-buffer-overflow-in-esp-transformation.patch
> > > and it can be found in the queue-4.19 subdirectory.
> > > 
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> > 
> > Oops, nope, sorry this breaks the build on 5.4 and older kernels, now
> > dropped.
> 
> Yes, that is for 5.10 only.

Can you provide a working backport for 4.14, 4.19, and 5.4?  They also
are affected here.

thanks,

greg k-h

      reply	other threads:[~2022-03-22  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16478662281158@kroah.com>
2022-03-21 13:12 ` Greg KH
2022-03-21 14:47   ` Tadeusz Struk
2022-03-21 15:53     ` 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=YjifgTsDes+hiKq6@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sec@valis.email \
    --cc=stable-commits@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=tadeusz.struk@linaro.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

all inboxes | Powered by JetHome®