Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Vlad Tsyrklevich <vlad@tsyrklevich.net>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v3] vfio/pci: Fix integer overflows, bitmask check
Date: Wed, 26 Oct 2016 15:19:18 -0600	[thread overview]
Message-ID: <20161026151918.7fcd3e07@t450s.home> (raw)
In-Reply-To: <1476291084-50737-1-git-send-email-vlad@tsyrklevich.net>

On Wed, 12 Oct 2016 18:51:24 +0200
Vlad Tsyrklevich <vlad@tsyrklevich.net> wrote:

> The VFIO_DEVICE_SET_IRQS ioctl did not sufficiently sanitize
> user-supplied integers, potentially allowing memory corruption. This
> patch adds appropriate integer overflow checks, checks the range bounds
> for VFIO_IRQ_SET_DATA_NONE, and also verifies that only single element
> in the VFIO_IRQ_SET_DATA_TYPE_MASK bitmask is set.
> VFIO_IRQ_SET_ACTION_TYPE_MASK is already correctly checked later in
> vfio_pci_set_irqs_ioctl().
> 
> Furthermore, a kzalloc is changed to a kcalloc because the use of a
> kzalloc with an integer multiplication allowed an integer overflow
> condition to be reached without this patch. kcalloc checks for overflow
> and should prevent a similar occurrence.
> 
> Signed-off-by: Vlad Tsyrklevich <vlad@tsyrklevich.net>
> ---
>  drivers/vfio/pci/vfio_pci.c       | 33 +++++++++++++++++++++------------
>  drivers/vfio/pci/vfio_pci_intrs.c |  2 +-
>  2 files changed, 22 insertions(+), 13 deletions(-)

I've applied this to my for-linus branch for v4.9, thanks,

Alex
 
> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> index d624a52..031bc08 100644
> --- a/drivers/vfio/pci/vfio_pci.c
> +++ b/drivers/vfio/pci/vfio_pci.c
> @@ -829,8 +829,9 @@ static long vfio_pci_ioctl(void *device_data,
>  
>  	} else if (cmd == VFIO_DEVICE_SET_IRQS) {
>  		struct vfio_irq_set hdr;
> +		size_t size;
>  		u8 *data = NULL;
> -		int ret = 0;
> +		int max, ret = 0;
>  
>  		minsz = offsetofend(struct vfio_irq_set, count);
>  
> @@ -838,23 +839,31 @@ static long vfio_pci_ioctl(void *device_data,
>  			return -EFAULT;
>  
>  		if (hdr.argsz < minsz || hdr.index >= VFIO_PCI_NUM_IRQS ||
> +		    hdr.count >= (U32_MAX - hdr.start) ||
>  		    hdr.flags & ~(VFIO_IRQ_SET_DATA_TYPE_MASK |
>  				  VFIO_IRQ_SET_ACTION_TYPE_MASK))
>  			return -EINVAL;
>  
> -		if (!(hdr.flags & VFIO_IRQ_SET_DATA_NONE)) {
> -			size_t size;
> -			int max = vfio_pci_get_irq_count(vdev, hdr.index);
> +		max = vfio_pci_get_irq_count(vdev, hdr.index);
> +		if (hdr.start >= max || hdr.start + hdr.count > max)
> +			return -EINVAL;
>  
> -			if (hdr.flags & VFIO_IRQ_SET_DATA_BOOL)
> -				size = sizeof(uint8_t);
> -			else if (hdr.flags & VFIO_IRQ_SET_DATA_EVENTFD)
> -				size = sizeof(int32_t);
> -			else
> -				return -EINVAL;
> +		switch (hdr.flags & VFIO_IRQ_SET_DATA_TYPE_MASK) {
> +		case VFIO_IRQ_SET_DATA_NONE:
> +			size = 0;
> +			break;
> +		case VFIO_IRQ_SET_DATA_BOOL:
> +			size = sizeof(uint8_t);
> +			break;
> +		case VFIO_IRQ_SET_DATA_EVENTFD:
> +			size = sizeof(int32_t);
> +			break;
> +		default:
> +			return -EINVAL;
> +		}
>  
> -			if (hdr.argsz - minsz < hdr.count * size ||
> -			    hdr.start >= max || hdr.start + hdr.count > max)
> +		if (size) {
> +			if (hdr.argsz - minsz < hdr.count * size)
>  				return -EINVAL;
>  
>  			data = memdup_user((void __user *)(arg + minsz),
> diff --git a/drivers/vfio/pci/vfio_pci_intrs.c b/drivers/vfio/pci/vfio_pci_intrs.c
> index c2e6089..1c46045 100644
> --- a/drivers/vfio/pci/vfio_pci_intrs.c
> +++ b/drivers/vfio/pci/vfio_pci_intrs.c
> @@ -256,7 +256,7 @@ static int vfio_msi_enable(struct vfio_pci_device *vdev, int nvec, bool msix)
>  	if (!is_irq_none(vdev))
>  		return -EINVAL;
>  
> -	vdev->ctx = kzalloc(nvec * sizeof(struct vfio_pci_irq_ctx), GFP_KERNEL);
> +	vdev->ctx = kcalloc(nvec, sizeof(struct vfio_pci_irq_ctx), GFP_KERNEL);
>  	if (!vdev->ctx)
>  		return -ENOMEM;
>  


      reply	other threads:[~2016-10-26 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 11:02 [PATCH] vfio/pci: Fix integer overflow/heap memory disclosure Vlad Tsyrklevich
2016-10-11 16:10 ` Alex Williamson
2016-10-11 20:04   ` Vlad Tsyrklevich
2016-10-11 22:39     ` Alex Williamson
2016-10-12  7:53       ` [PATCH v2] vfio/pci: Fix integer overflows, bitmask check Vlad Tsyrklevich
2016-10-12 14:51         ` Alex Williamson
2016-10-12 15:06           ` Vlad Tsyrklevich
2016-10-12 15:39             ` Alex Williamson
2016-10-12 16:51               ` [PATCH v3] " Vlad Tsyrklevich
2016-10-26 21:19                 ` Alex Williamson [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=20161026151918.7fcd3e07@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=vlad@tsyrklevich.net \
    /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