From: Avihai Horon <avihaih@nvidia.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH] vfio: Fix null pointer dereference bug in vfio_bars_finalize()
Date: Tue, 4 Jul 2023 13:51:00 +0300 [thread overview]
Message-ID: <e3c825f9-dbe1-01a3-a078-a18f6f9af18c@nvidia.com> (raw)
In-Reply-To: <7c4c2bc7-add6-6e45-c753-af163de3e216@linaro.org>
On 03/07/2023 19:56, Philippe Mathieu-Daudé wrote:
> External email: Use caution opening links or attachments
>
>
> On 3/7/23 18:39, Avihai Horon wrote:
>> vfio_realize() has the following flow:
>> 1. vfio_bars_prepare() -- sets VFIOBAR->size.
>> 2. msix_early_setup().
>> 3. vfio_bars_register() -- allocates VFIOBAR->mr.
>>
>> After vfio_bars_prepare() is called msix_early_setup() can fail. If it
>> does fail, vfio_bars_register() is never called and VFIOBAR->mr is not
>> allocated.
>>
>> In this case, vfio_bars_finalize() is called as part of the error flow
>> to free the bars' resources. However, vfio_bars_finalize() calls
>> object_unparent() for VFIOBAR->mr unconditionally and thus we get a null
>> pointer dereference.
>>
>> Fix it by checking VFIOBAR->mr in vfio_bars_finalize().
>>
>> Fixes: 89d5202edc50 ("vfio/pci: Allow relocating MSI-X MMIO")
>> Signed-off-by: Avihai Horon <avihaih@nvidia.com>
>> ---
>> hw/vfio/pci.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
>> index ab6645ba60..95e077082b 100644
>> --- a/hw/vfio/pci.c
>> +++ b/hw/vfio/pci.c
>> @@ -1752,7 +1752,7 @@ static void vfio_bars_finalize(VFIOPCIDevice
>> *vdev)
>>
>> vfio_bar_quirk_finalize(vdev, i);
>> vfio_region_finalize(&bar->region);
>> - if (bar->size) {
>> + if (bar->size && bar->mr) {
>> object_unparent(OBJECT(bar->mr));
>> g_free(bar->mr);
>> }
>
> What about:
>
> if (bar->mr) {
> assert(bar->size);
> object_unparent(OBJECT(bar->mr));
> g_free(bar->mr);
> bar->mr = NULL;
> }
>
> ?
Nice touch, it's indeed more accurate.
Will change and post v2.
Thanks!
prev parent reply other threads:[~2023-07-04 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 16:39 [PATCH] vfio: Fix null pointer dereference bug in vfio_bars_finalize() Avihai Horon
2023-07-03 16:56 ` Philippe Mathieu-Daudé
2023-07-04 10:51 ` Avihai Horon [this message]
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=e3c825f9-dbe1-01a3-a078-a18f6f9af18c@nvidia.com \
--to=avihaih@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).