public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Brennan Lamoreaux <brennan.lamoreaux@broadcom.com>
Cc: stable@vger.kernel.org, phaddad@nvidia.com,
	shiraz.saleem@intel.com, ajay.kaher@broadcom.com
Subject: Re: Backport fix for CVE-2023-2176 (8d037973 and 0e158630) to v6.1
Date: Wed, 28 Feb 2024 05:46:52 +0100	[thread overview]
Message-ID: <2024022817-remedial-agonize-2e34@gregkh> (raw)
In-Reply-To: <20240228001506.3693-1-brennan.lamoreaux@broadcom.com>

On Tue, Feb 27, 2024 at 04:15:06PM -0800, Brennan Lamoreaux wrote:
> Hi stable maintainers,
> 
> The following patch in mainline is listed as a fix for CVE-2023-2176:
> 8d037973d48c026224ab285e6a06985ccac6f7bf (RDMA/core: Refactor rdma_bind_addr)
> 
> And the following is a fix for a regression in the above patch:
> 0e15863015d97c1ee2cc29d599abcc7fa2dc3e95 (RDMA/core: Update CMA destination address on rdma_resolve_addr)
> 
> To my knowledge, at least back to v6.1 is vulnerable to this same bug.
> Since these should apply directly to 6.1.y, can these be picked up for that branch?

If you provide a working backport of that commit, we will be glad to
apply it.  As-is, it does not apply at all, which is why it was never
added to the 6.1.y tree.

thanks,

greg k-h

  reply	other threads:[~2024-02-28  4:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  0:15 Backport fix for CVE-2023-2176 (8d037973 and 0e158630) to v6.1 Brennan Lamoreaux
2024-02-28  4:46 ` Greg KH [this message]
2024-02-28 18:41   ` Brennan Lamoreaux
2024-02-29  8:35     ` Ajay Kaher
2024-03-04  6:44       ` Greg KH
2024-03-04  8:51         ` Ajay Kaher
2024-03-04  9:20           ` Greg KH
2024-03-04  9:41             ` Ajay Kaher

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=2024022817-remedial-agonize-2e34@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ajay.kaher@broadcom.com \
    --cc=brennan.lamoreaux@broadcom.com \
    --cc=phaddad@nvidia.com \
    --cc=shiraz.saleem@intel.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