public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Vaibhav Rustagi <vaibhavrustagi@google.com>
Cc: "# 3.4.x" <stable@vger.kernel.org>, steffen.klassert@secunet.com
Subject: Re: Cherry-pick request to fix CVE-2022-0886 in v5.10 and v5.4
Date: Tue, 22 Mar 2022 09:02:15 +0100	[thread overview]
Message-ID: <YjmCh1SPUOJjM7Rf@kroah.com> (raw)
In-Reply-To: <CAMVonLjSP4cxtfahDORXG-b6K=ps+wN652hcrxgo70YU+eP5iA@mail.gmail.com>

On Mon, Mar 21, 2022 at 06:49:02PM -0700, Vaibhav Rustagi wrote:
> Hi Greg,
> 
> To fix CVE-2022-0886 in v5.10 and v5.4, we need to cherry-pick the
> commit "esp: Fix possible buffer overflow in ESP transformation"
> (ebe48d368e97d007bfeb76fcb065d6cfc4c96645). The commit didn't apply
> cleanly in v5.10 and v5.4 and therefore, patches for both the kernel
> versions are attached.
> 
> In order to backport the original commit, following changes are done:
> 
>  - v5.10:
>     - "SKB_FRAG_PAGE_ORDER" declaration is moved from
> "net/core/sock.c" to "include/net/sock.c"

Did you see that this is already in the 5.10 queue and out for review
right now?  Can you verify that the backport there matches yours?

>  - v5.4:
>     - "SKB_FRAG_PAGE_ORDER" declaration is moved from
> "net/core/sock.c" to "include/net/sock.c"
>     - Ignore changes introduced due to `xfrm: add support for UDPv6
> encapsulation of ESP` in esp6_output_head()

Thanks for this one, I'll queue it up after this next round of releases.
What about 4.14 and 4.19?  Will this backport work there?  If not, can
you provide a working one?

thanks,

greg k-h

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  1:49 Cherry-pick request to fix CVE-2022-0886 in v5.10 and v5.4 Vaibhav Rustagi
2022-03-22  8:02 ` Greg KH [this message]
2022-03-22 16:53   ` Vaibhav Rustagi
2022-03-22 20:42     ` Vaibhav Rustagi
2022-03-24 14:22       ` Greg KH
2022-03-23  7:01     ` Greg KH
2022-03-23 16:14       ` Vaibhav Rustagi

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=YjmCh1SPUOJjM7Rf@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=vaibhavrustagi@google.com \
    /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