From: Greg KH <gregkh@linuxfoundation.org>
To: Dragos-Marian Panait <dragos.panait@windriver.com>
Cc: stable@vger.kernel.org, Ruihan Li <lrh2000@pku.edu.cn>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Johan Hedberg <johan.hedberg@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4.14 0/1] Hardening against CVE-2023-2002
Date: Tue, 30 May 2023 14:42:55 +0100 [thread overview]
Message-ID: <2023053030-moaning-endanger-ac26@gregkh> (raw)
In-Reply-To: <20230530131740.269890-1-dragos.panait@windriver.com>
On Tue, May 30, 2023 at 04:17:39PM +0300, Dragos-Marian Panait wrote:
> The following commit is needed to harden against CVE-2023-2002:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=000c2fa2c144c499c881a101819cf1936a1f7cf2
>
> Ruihan Li (1):
> bluetooth: Add cmd validity checks at the start of hci_sock_ioctl()
>
> net/bluetooth/hci_sock.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
>
> base-commit: b3f141a5bc7f877e96528dd31a139854ec4d6017
> --
> 2.40.1
>
Nit, for 1 patch series, no need for a cover letter, you can put the
same info below the --- line if that's easier.
thanks,
greg k-h
prev parent reply other threads:[~2023-05-30 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 13:17 [PATCH 4.14 0/1] Hardening against CVE-2023-2002 Dragos-Marian Panait
2023-05-30 13:17 ` [PATCH 4.14 1/1] bluetooth: Add cmd validity checks at the start of hci_sock_ioctl() Dragos-Marian Panait
2023-05-30 13:42 ` 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=2023053030-moaning-endanger-ac26@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=dragos.panait@windriver.com \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrh2000@pku.edu.cn \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).