[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <796c9d73-30a0-2401-e499-724aeb0f8dc6@redhat.com>
Date: Wed, 31 Aug 2022 17:01:11 +0200
From: Maxime Coquelin <maxime.coquelin@...hat.com>
To: jasowang@...hat.com, Greg KH <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, elic@...dia.com,
guanjun@...ux.alibaba.com, parav@...dia.com,
gautam.dawar@...inx.com, dan.carpenter@...cle.com,
xieyongji@...edance.com, mst@...hat.com, stable@...r.kernel.org
Subject: Re: [PATCH v2] vduse: prevent uninitialized memory accesses
On 8/29/22 09:48, Greg KH wrote:
> On Mon, Aug 29, 2022 at 09:34:24AM +0200, Maxime Coquelin wrote:
>> If the VDUSE application provides a smaller config space
>> than the driver expects, the driver may use uninitialized
>> memory from the stack.
>>
>> This patch prevents it by initializing the buffer passed by
>> the driver to store the config value.
>>
>> This fix addresses CVE-2022-2308.
>>
>> Cc: xieyongji@...edance.com
>> Cc: stable@...r.kernel.org # v5.15+
>> Fixes: c8a6153b6c59 ("vduse: Introduce VDUSE - vDPA Device in Userspace")
>>
>> Acked-by: Jason Wang <jasowang@...hat.com>
>> Signed-off-by: Maxime Coquelin <maxime.coquelin@...hat.com>
>
> Please no blank line above the Acked-by: line here if possible.
Sure.
Jason, do you prefer I post a new revision with this single change or
you will handle it while applying? Either way is fine to me.
Thanks,
Maxime
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists