diff options
| author | Albert Esteve <aesteve@redhat.com> | 2024-02-19 15:34:19 +0100 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2024-03-12 17:56:55 -0400 |
| commit | 043e127a126bb3ceb5fc753deee27d261fd0c5ce (patch) | |
| tree | d46031e527c6137973353582c1f33b530541f395 /README.rst | |
| parent | 633487df8d303b37a88584d5a57a39dbcd91c7bf (diff) | |
| download | qemu-043e127a126bb3ceb5fc753deee27d261fd0c5ce.zip qemu-043e127a126bb3ceb5fc753deee27d261fd0c5ce.tar.gz qemu-043e127a126bb3ceb5fc753deee27d261fd0c5ce.tar.bz2 | |
hw/virtio: check owner for removing objects
Shared objects lack spoofing protection.
For VHOST_USER_BACKEND_SHARED_OBJECT_REMOVE messages
received by the vhost-user interface, any backend was
allowed to remove entries from the shared table just
by knowing the UUID. Only the owner of the entry
shall be allowed to removed their resources
from the table.
To fix that, add a check for all
*SHARED_OBJECT_REMOVE messages received.
A vhost device can only remove TYPE_VHOST_DEV
entries that are owned by them, otherwise skip
the removal, and inform the device that the entry
has not been removed in the answer.
Signed-off-by: Albert Esteve <aesteve@redhat.com>
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20240219143423.272012-2-aesteve@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'README.rst')
0 files changed, 0 insertions, 0 deletions