[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y7VzLI/GhGtne+78@kroah.com>
Date: Wed, 4 Jan 2023 13:38:04 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Dragos-Marian Panait <dragos.panait@...driver.com>
Cc: stable@...r.kernel.org, Jiasheng Jiang <jiasheng@...as.ac.cn>,
Felix Kuehling <Felix.Kuehling@....com>,
Alex Deucher <alexander.deucher@....com>,
Oded Gabbay <oded.gabbay@...il.com>,
Christian König <christian.koenig@....com>,
David Zhou <David1.Zhou@....com>,
David Airlie <airlied@...ux.ie>,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4.19 0/1] drm/amdkfd: Check for null pointer after
calling kmemdup
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}
Powered by blists - more mailing lists