linux-kernel - Re: [PATCH 0/7] Do not read from descriptor ring

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 10 Jun 2021 11:12:56 +0800
From:   Jason Wang <jasowang@...hat.com>
To:     Andy Lutomirski <luto@...nel.org>, mst@...hat.com
Cc:     virtualization@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org, xieyongji@...edance.com,
        stefanha@...hat.com, file@...t.tu-berlin.de, ashish.kalra@....com,
        konrad.wilk@...cle.com, kvm@...r.kernel.org, hch@...radead.org,
        ak@...ux.intel.com
Subject: Re: [PATCH 0/7] Do not read from descriptor ring


在 2021/6/9 上午12:24, Andy Lutomirski 写道:
> On 6/3/21 10:53 PM, Jason Wang wrote:
>> Hi:
>>
>> The virtio driver should not trust the device. This beame more urgent
>> for the case of encrtpyed VM or VDUSE[1]. In both cases, technology
>> like swiotlb/IOMMU is used to prevent the poking/mangling of memory
>> from the device. But this is not sufficient since current virtio
>> driver may trust what is stored in the descriptor table (coherent
>> mapping) for performing the DMA operations like unmap and bounce so
>> the device may choose to utilize the behaviour of swiotlb to perform
>> attacks[2].
> Based on a quick skim, this looks entirely reasonable to me.
>
> (I'm not a virtio maintainer or expert.  I got my hands very dirty with
> virtio once dealing with the DMA mess, but that's about it.)
>
> --Andy


Good to know that :)

Thanks