25.09.2024 13:23, Mattias Nissler wrote:
On Wed, Sep 25, 2024 at 12:03 PM Michael Tokarev <mjt@tls.msk.ru> wrote:
..
So, the issue has now become CVE-2024-8612 (information leak), with this
commit (v9.1.0-134-g637b0aa139) being the fix.
Interesting. IIUC, this is triggered by device implementations calling
dma_memory_unmap with an incorrect size parameter as provided by a
hostile guest. Shouldn't the device implementations be fixed to
validate the parameter as well? Maybe this has already happened? It
would seem the more targeted fix to me.
Yes, a similar question occurred to me too, - this change does not look
like a proper fix for CVE-2024-8612. And nope, no other changes has been
made to fix it properly, in the device implementations.
Maybe now with CVE-2024-8612 in place, we can fix the actual problem in
the right place, instead of relying on this change..