public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] vfio/type1: fix cap_migration information leak
Date: Tue, 1 Aug 2023 15:23:45 -0400	[thread overview]
Message-ID: <20230801192345.GA1414936@fedora> (raw)
In-Reply-To: <20230801103114.757d7992.alex.williamson@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2777 bytes --]

On Tue, Aug 01, 2023 at 10:31:14AM -0600, Alex Williamson wrote:
> On Tue,  1 Aug 2023 11:53:52 -0400
> Stefan Hajnoczi <stefanha@redhat.com> wrote:
> 
> > Fix an information leak where an uninitialized hole in struct
> > vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace.
> > 
> > The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as
> > shown in this pahole(1) output:
> > 
> >   struct vfio_iommu_type1_info_cap_migration {
> >           struct vfio_info_cap_header header;              /*     0     8 */
> >           __u32                      flags;                /*     8     4 */
> > 
> >           /* XXX 4 bytes hole, try to pack */
> > 
> >           __u64                      pgsize_bitmap;        /*    16     8 */
> >           __u64                      max_dirty_bitmap_size; /*    24     8 */
> > 
> >           /* size: 32, cachelines: 1, members: 4 */
> >           /* sum members: 28, holes: 1, sum holes: 4 */
> >           /* last cacheline: 32 bytes */
> >   };
> > 
> > The cap_mig variable is filled in without initializing the hole:
> > 
> >   static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,
> >                          struct vfio_info_cap *caps)
> >   {
> >       struct vfio_iommu_type1_info_cap_migration cap_mig;
> > 
> >       cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;
> >       cap_mig.header.version = 1;
> > 
> >       cap_mig.flags = 0;
> >       /* support minimum pgsize */
> >       cap_mig.pgsize_bitmap = (size_t)1 << __ffs(iommu->pgsize_bitmap);
> >       cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;
> > 
> >       return vfio_info_add_capability(caps, &cap_mig.header, sizeof(cap_mig));
> >   }
> > 
> > The structure is then copied to a temporary location on the heap. At this point
> > it's already too late and ioctl(VFIO_IOMMU_GET_INFO) copies it to userspace
> > later:
> > 
> >   int vfio_info_add_capability(struct vfio_info_cap *caps,
> >                    struct vfio_info_cap_header *cap, size_t size)
> >   {
> >       struct vfio_info_cap_header *header;
> > 
> >       header = vfio_info_cap_add(caps, size, cap->id, cap->version);
> >       if (IS_ERR(header))
> >           return PTR_ERR(header);
> > 
> >       memcpy(header + 1, cap + 1, size - sizeof(*header));
> > 
> >       return 0;
> >   }
> > 
> > This issue was found by code inspection.
> 
> LGTM, but missing:
> 
> Fixes: ad721705d09c ("vfio iommu: Add migration capability to report supported features")
> 
> I'll give a bit for further comments/reviews and queue it for v6.6 with
> the above update.  Thanks,

Great, thanks for squashing in the "Fixes" line that I forgot.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-08-01 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 15:53 [PATCH] vfio/type1: fix cap_migration information leak Stefan Hajnoczi
2023-08-01 16:31 ` Alex Williamson
2023-08-01 19:23   ` Stefan Hajnoczi [this message]
2023-08-03  5:19 ` Tian, Kevin
2023-08-17 17:55 ` Alex Williamson

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=20230801192345.GA1414936@fedora \
    --to=stefanha@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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