From: Greg KH <gregkh@linuxfoundation.org>
To: "Saleem, Shiraz" <shiraz.saleem@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"security@kernel.org" <security@kernel.org>,
"Ismail, Mustafa" <mustafa.ismail@intel.com>
Subject: Re: Security Fix Backport: Intel RDMA driver
Date: Mon, 30 Oct 2023 18:25:38 +0100 [thread overview]
Message-ID: <2023103015-footpath-veggie-63fb@gregkh> (raw)
In-Reply-To: <MWHPR11MB00293EBF6DD3DAA4C836E382E9A1A@MWHPR11MB0029.namprd11.prod.outlook.com>
On Mon, Oct 30, 2023 at 04:47:01PM +0000, Saleem, Shiraz wrote:
> Hi,
>
> There was a security bug fix recently made to the Intel RDMA driver (irdma) that has made to mainline.
>
> https://github.com/torvalds/linux/commit/bb6d73d9add68ad270888db327514384dfa44958
> subject: RDMA/irdma: Prevent zero-length STAG registration
> commit-id: bb6d73d9add68ad270888db327514384dfa44958
>
> This problem in theory is possible in i40iw as well. i40iw is replaced with irdma upstream since 5.14.
>
> However, i40iw is still part of LTS 4.14.x, 4.19.x, 5.4.x, and 5.10. Since it is a security fix, I am thinking its reasonable we backport it to i40iw too for these kernels. The patch would need some adjustments and I can do this if required.
If you feel it is needed, yes, please do the needed backport and submit
it here.
thanks,
greg k-h
next parent reply other threads:[~2023-10-30 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MWHPR11MB00293EBF6DD3DAA4C836E382E9A1A@MWHPR11MB0029.namprd11.prod.outlook.com>
2023-10-30 17:25 ` Greg KH [this message]
2023-10-31 1:21 ` Security Fix Backport: Intel RDMA driver Saleem, Shiraz
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=2023103015-footpath-veggie-63fb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=mustafa.ismail@intel.com \
--cc=security@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.