From: Greg KH <gregkh@linuxfoundation.org>
To: Dragos-Marian Panait <dragos.panait@windriver.com>
Cc: stable@vger.kernel.org, "Jiasheng Jiang" <jiasheng@iscas.ac.cn>,
"Felix Kuehling" <Felix.Kuehling@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Oded Gabbay" <oded.gabbay@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"David Zhou" <David1.Zhou@amd.com>,
"David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4.19 0/1] drm/amdkfd: Check for null pointer after calling kmemdup
Date: Wed, 4 Jan 2023 13:38:04 +0100 [thread overview]
Message-ID: <Y7VzLI/GhGtne+78@kroah.com> (raw)
In-Reply-To: <20230103184308.511448-1-dragos.panait@windriver.com>
On Tue, Jan 03, 2023 at 08:43:07PM +0200, Dragos-Marian Panait wrote:
> The following commit is needed to fix CVE-2022-3108:
That's a funny cve, given that you can not ever trigger it in a system,
right? Why was a CVE allocated for that?
{sigh}
prev parent reply other threads:[~2023-01-04 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 18:43 [PATCH 4.19 0/1] drm/amdkfd: Check for null pointer after calling kmemdup Dragos-Marian Panait
2023-01-03 18:43 ` [PATCH 4.19 1/1] " Dragos-Marian Panait
2023-01-04 12:41 ` Greg KH
2023-01-04 13:22 ` Christian König
2023-01-04 14:35 ` Alex Deucher
2023-01-04 14:48 ` Greg KH
2023-01-04 18:05 ` Dragos-Marian Panait
2023-01-05 8:01 ` Greg KH
2023-01-04 12:38 ` 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=Y7VzLI/GhGtne+78@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=David1.Zhou@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dragos.panait@windriver.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jiasheng@iscas.ac.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.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