From: Alex Williamson <alex@shazbot.org>
To: Yousef Alhouseen <alhouseenyousef@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
alex@shazbot.org, lirongqing <lirongqing@baidu.com>
Subject: Re: [PATCH] vfio/type1: validate dirty bitmap page size before use
Date: Wed, 24 Jun 2026 13:22:17 -0600 [thread overview]
Message-ID: <20260624132217.7fd42c77@shazbot.org> (raw)
In-Reply-To: <20260624191204.3774-1-alhouseenyousef@gmail.com>
On Wed, 24 Jun 2026 21:12:04 +0200
Yousef Alhouseen <alhouseenyousef@gmail.com> wrote:
> The dirty bitmap ioctl paths derive a shift with __ffs() from the
> userspace supplied bitmap page size before comparing it with the IOMMU
> page size. A zero page size has undefined behavior, and a non-power-of-2
> value makes the bitmap size check use a different granularity than the
> page size later accepted by the ioctl.
>
> Reject invalid bitmap page sizes before using them in shift arithmetic.
Thanks for the patch, this is already being worked:
[v1]https://lore.kernel.org/all/20260616111733.1810-1-lirongqing@baidu.com/
[v2]https://lore.kernel.org/all/20260617113251.2535-1-lirongqing@baidu.com/
Thanks,
Alex
> Signed-off-by: Yousef Alhouseen <alhouseenyousef@gmail.com>
> ---
> drivers/vfio/vfio_iommu_type1.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index c8151ba54..9499381d0 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -26,6 +26,7 @@
> #include <linux/fs.h>
> #include <linux/highmem.h>
> #include <linux/iommu.h>
> +#include <linux/log2.h>
> #include <linux/module.h>
> #include <linux/mm.h>
> #include <linux/kthread.h>
> @@ -2949,6 +2950,9 @@ static int vfio_iommu_type1_unmap_dma(struct vfio_iommu *iommu,
> if (!access_ok((void __user *)bitmap.data, bitmap.size))
> return -EINVAL;
>
> + if (!is_power_of_2(bitmap.pgsize))
> + return -EINVAL;
> +
> pgshift = __ffs(bitmap.pgsize);
> ret = verify_bitmap_size(unmap.size >> pgshift,
> bitmap.size);
> @@ -3039,6 +3043,9 @@ static int vfio_iommu_type1_dirty_pages(struct vfio_iommu *iommu,
> range.bitmap.size))
> return -EINVAL;
>
> + if (!is_power_of_2(range.bitmap.pgsize))
> + return -EINVAL;
> +
> pgshift = __ffs(range.bitmap.pgsize);
> ret = verify_bitmap_size(size >> pgshift,
> range.bitmap.size);
next prev parent reply other threads:[~2026-06-24 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 19:12 [PATCH] vfio/type1: validate dirty bitmap page size before use Yousef Alhouseen
2026-06-24 19:22 ` Alex Williamson [this message]
2026-06-24 19:25 ` sashiko-bot
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=20260624132217.7fd42c77@shazbot.org \
--to=alex@shazbot.org \
--cc=alhouseenyousef@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.