qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/vfio/pci-quirks: Sanitize capability pointer
Date: Mon, 3 Jul 2023 08:07:16 +0200	[thread overview]
Message-ID: <a09bb627-ba8e-a7e4-3969-9933a89e30cc@redhat.com> (raw)
In-Reply-To: <20230630223608.650555-1-alex.williamson@redhat.com>

On 7/1/23 00:36, Alex Williamson wrote:
> Coverity reports a tained scalar when traversing the capabilities
> chain (CID 1516589).  In practice I've never seen a device with a
> chain so broken as to cause an issue, but it's also pretty easy to
> sanitize.
> 
> Fixes: f6b30c1984f7 ("hw/vfio/pci-quirks: Support alternate offset for GPUDirect Cliques")
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>

Reviewed-by: Cédric Le Goater <clg@redhat.com>

Nice. I was just looking at the coverity report ! You beat me at it.

is_valid_std_cap_offset() could be reused in other places where QEMU
scans the PCI capabilities I think.

Thanks,

C.

> ---
>   hw/vfio/pci-quirks.c | 10 ++++++++--
>   1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/vfio/pci-quirks.c b/hw/vfio/pci-quirks.c
> index 0ed2fcd53152..f4ff83680572 100644
> --- a/hw/vfio/pci-quirks.c
> +++ b/hw/vfio/pci-quirks.c
> @@ -1530,6 +1530,12 @@ const PropertyInfo qdev_prop_nv_gpudirect_clique = {
>       .set = set_nv_gpudirect_clique_id,
>   };
>   
> +static bool is_valid_std_cap_offset(uint8_t pos)
> +{
> +    return (pos >= PCI_STD_HEADER_SIZEOF &&
> +            pos <= (PCI_CFG_SPACE_SIZE - PCI_CAP_SIZEOF));
> +}
> +
>   static int vfio_add_nv_gpudirect_cap(VFIOPCIDevice *vdev, Error **errp)
>   {
>       PCIDevice *pdev = &vdev->pdev;
> @@ -1563,7 +1569,7 @@ static int vfio_add_nv_gpudirect_cap(VFIOPCIDevice *vdev, Error **errp)
>        */
>       ret = pread(vdev->vbasedev.fd, &tmp, 1,
>                   vdev->config_offset + PCI_CAPABILITY_LIST);
> -    if (ret != 1 || !tmp) {
> +    if (ret != 1 || !is_valid_std_cap_offset(tmp)) {
>           error_setg(errp, "NVIDIA GPUDirect Clique ID: error getting cap list");
>           return -EINVAL;
>       }
> @@ -1575,7 +1581,7 @@ static int vfio_add_nv_gpudirect_cap(VFIOPCIDevice *vdev, Error **errp)
>               d4_conflict = true;
>           }
>           tmp = pdev->config[tmp + PCI_CAP_LIST_NEXT];
> -    } while (tmp);
> +    } while (is_valid_std_cap_offset(tmp));
>   
>       if (!c8_conflict) {
>           pos = 0xC8;



      reply	other threads:[~2023-07-03  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 22:36 [PATCH] hw/vfio/pci-quirks: Sanitize capability pointer Alex Williamson
2023-07-03  6:07 ` Cédric Le Goater [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=a09bb627-ba8e-a7e4-3969-9933a89e30cc@redhat.com \
    --to=clg@redhat.com \
    --cc=alex.williamson@redhat.com \
    --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).