public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xiangyu Chen <xiangyu.chen@eng.windriver.com>
Cc: edumazet@google.com, stable@vger.kernel.org, xiangyu.chen@aol.com
Subject: Re: [PATCH 6.1.y 0/2] Backport fix of CVE-2024-36915 to 6.1
Date: Tue, 19 Nov 2024 14:10:22 +0100	[thread overview]
Message-ID: <2024111916-platform-finale-7bd5@gregkh> (raw)
In-Reply-To: <20241119020537.3050784-1-xiangyu.chen@eng.windriver.com>

On Tue, Nov 19, 2024 at 10:05:35AM +0800, Xiangyu Chen wrote:
> From: Xiangyu Chen <xiangyu.chen@windriver.com>
> 
> Following series is a backport of CVE-2024-36915
> 
> The fix is "nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies"
> This required 1 extra commit to make sure the picks are clean:
> net: add copy_safe_from_sockptr() helper
> 
> 
> Eric Dumazet (2):
>   net: add copy_safe_from_sockptr() helper
>   nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies
> 
>  include/linux/sockptr.h | 25 +++++++++++++++++++++++++
>  net/nfc/llcp_sock.c     | 12 ++++++------
>  2 files changed, 31 insertions(+), 6 deletions(-)
> 
> -- 
> 2.43.0
> 
> 

Now queued up, thanks.

greg k-h

      parent reply	other threads:[~2024-11-19 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19  2:05 [PATCH 6.1.y 0/2] Backport fix of CVE-2024-36915 to 6.1 Xiangyu Chen
2024-11-19  2:05 ` [PATCH 6.1.y 1/2] net: add copy_safe_from_sockptr() helper Xiangyu Chen
2024-11-19 12:31   ` Sasha Levin
2024-11-19  2:05 ` [PATCH 6.1.y 2/2] nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies Xiangyu Chen
2024-11-19 12:31   ` Sasha Levin
2024-11-19 13:10 ` 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=2024111916-platform-finale-7bd5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=edumazet@google.com \
    --cc=stable@vger.kernel.org \
    --cc=xiangyu.chen@aol.com \
    --cc=xiangyu.chen@eng.windriver.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