From: Avihai Horon <avihaih@nvidia.com>
To: <qemu-devel@nongnu.org>
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Eric Farman" <farman@linux.ibm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"David Hildenbrand" <david@redhat.com>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Thomas Huth" <thuth@redhat.com>,
"Juan Quintela" <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Fam Zheng" <fam@euphon.net>, "Eric Blake" <eblake@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
"John Snow" <jsnow@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
qemu-s390x@nongnu.org, qemu-block@nongnu.org,
"Yishai Hadas" <yishaih@nvidia.com>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Maor Gottlieb" <maorg@nvidia.com>,
"Avihai Horon" <avihaih@nvidia.com>,
"Kirti Wankhede" <kwankhede@nvidia.com>,
"Tarun Gupta" <targupta@nvidia.com>,
"Joao Martins" <joao.m.martins@oracle.com>
Subject: [PATCH v6 03/13] vfio/migration: Fix NULL pointer dereference bug
Date: Thu, 12 Jan 2023 10:50:10 +0200 [thread overview]
Message-ID: <20230112085020.15866-4-avihaih@nvidia.com> (raw)
In-Reply-To: <20230112085020.15866-1-avihaih@nvidia.com>
As part of its error flow, vfio_vmstate_change() accesses
MigrationState->to_dst_file without any checks. This can cause a NULL
pointer dereference if the error flow is taken and
MigrationState->to_dst_file is not set.
For example, this can happen if VM is started or stopped not during
migration and vfio_vmstate_change() error flow is taken, as
MigrationState->to_dst_file is not set at that time.
Fix it by checking that MigrationState->to_dst_file is set before using
it.
Fixes: 02a7e71b1e5b ("vfio: Add VM state change handler to know state of VM")
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
---
hw/vfio/migration.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/vfio/migration.c b/hw/vfio/migration.c
index e1413ac90c..09fe7c1de2 100644
--- a/hw/vfio/migration.c
+++ b/hw/vfio/migration.c
@@ -743,7 +743,9 @@ static void vfio_vmstate_change(void *opaque, bool running, RunState state)
*/
error_report("%s: Failed to set device state 0x%x", vbasedev->name,
(migration->device_state & mask) | value);
- qemu_file_set_error(migrate_get_current()->to_dst_file, ret);
+ if (migrate_get_current()->to_dst_file) {
+ qemu_file_set_error(migrate_get_current()->to_dst_file, ret);
+ }
}
vbasedev->migration->vm_running = running;
trace_vfio_vmstate_change(vbasedev->name, running, RunState_str(state),
--
2.26.3
next prev parent reply other threads:[~2023-01-12 8:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 8:50 [PATCH v6 00/13] vfio/migration: Implement VFIO migration protocol v2 Avihai Horon
2023-01-12 8:50 ` [PATCH v6 01/13] linux-headers: Update to v6.2-rc1 Avihai Horon
2023-01-12 8:50 ` [PATCH v6 02/13] migration: No save_live_pending() method uses the QEMUFile parameter Avihai Horon
2023-01-12 8:50 ` Avihai Horon [this message]
2023-01-12 8:50 ` [PATCH v6 04/13] vfio/migration: Allow migration without VFIO IOMMU dirty tracking support Avihai Horon
2023-01-12 8:50 ` [PATCH v6 05/13] migration/qemu-file: Add qemu_file_get_to_fd() Avihai Horon
2023-01-12 14:43 ` Cédric Le Goater
2023-01-12 8:50 ` [PATCH v6 06/13] vfio/common: Change vfio_devices_all_running_and_saving() logic to equivalent one Avihai Horon
2023-01-13 15:46 ` Cédric Le Goater
2023-01-12 8:50 ` [PATCH v6 07/13] vfio/migration: Move migration v1 logic to vfio_migration_init() Avihai Horon
2023-01-12 8:50 ` [PATCH v6 08/13] vfio/migration: Rename functions/structs related to v1 protocol Avihai Horon
2023-01-12 8:50 ` [PATCH v6 09/13] vfio/migration: Implement VFIO migration protocol v2 Avihai Horon
2023-01-13 16:13 ` Cédric Le Goater
2023-01-15 18:42 ` Avihai Horon
2023-01-12 8:50 ` [PATCH v6 10/13] vfio/migration: Optimize vfio_save_pending() Avihai Horon
2023-01-13 16:05 ` Cédric Le Goater
2023-01-12 8:50 ` [PATCH v6 11/13] vfio/migration: Remove VFIO migration protocol v1 Avihai Horon
2023-01-13 16:06 ` Cédric Le Goater
2023-01-12 8:50 ` [PATCH v6 12/13] vfio: Alphabetize migration section of VFIO trace-events file Avihai Horon
2023-01-13 16:06 ` Cédric Le Goater
2023-01-12 8:50 ` [PATCH v6 13/13] docs/devel: Align VFIO migration docs to v2 protocol Avihai Horon
2023-01-13 17:12 ` Cédric Le Goater
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230112085020.15866-4-avihaih@nvidia.com \
--to=avihaih@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=jsnow@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=targupta@nvidia.com \
--cc=thuth@redhat.com \
--cc=vsementsov@yandex-team.ru \
--cc=yishaih@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).