From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Laight <david.laight.linux@gmail.com>
Cc: Haoran Wang <haoranwangsec@gmail.com>,
jasowangio@gmail.com, kvm@vger.kernel.org,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
eperezma@redhat.com, linux-kernel@vger.kernel.org,
security@kernel.org
Subject: Re: [BUG] vhost/vringh: __get_user without access_ok leaks kernel memory via vDPA passthrough
Date: Sun, 18 Oct 2026 17:42:28 -0400 [thread overview]
Message-ID: <20261018174144-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20261018204838.4080b238@pumpkin>
On Sun, Oct 18, 2026 at 08:48:38PM +0100, David Laight wrote:
> On Sun, 18 Oct 2026 15:24:41 -0400
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Thu, Oct 15, 2026 at 03:23:45PM +0800, Haoran Wang wrote:
> > > I'd like to report an issue in drivers/vhost/vringh.c:1216 (function
> > > getu16_iotlb), found via static analysis of Linux 7.0.11 and verified
> > > against the 7.2.10 source tree. I have reproduced the leak on an
> > > unmodified 7.2.10 kernel.
> >
> >
> > This should fix it I think? Can you confirm pls?
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > drivers/vhost/vringh.c | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/vhost/vringh.c b/drivers/vhost/vringh.c
> > index 9066f9f12ba1..4b097170bd36 100644
> > --- a/drivers/vhost/vringh.c
> > +++ b/drivers/vhost/vringh.c
> > @@ -1213,7 +1213,11 @@ static inline int getu16_iotlb(const struct vringh *vrh,
> > return ret;
> >
> > if (vrh->use_va) {
> > - ret = __get_user(tmp, (__virtio16 __user *)ivec.iov.iovec[0].iov_base);
> > + __virtio16 __user *uaddr = ivec.iov.iovec[0].iov_base;
> > +
> > + if (!access_ok(uaddr, sizeof(*p)))
> > + return -EFAULT;
> > + ret = __get_user(tmp, uaddr);
>
> Can't that be a normal get_user() call?
>
> David
Now that you mention it, yes. Thanks!
> > if (ret)
> > return ret;
> > } else {
> > @@ -1251,7 +1255,11 @@ static inline int putu16_iotlb(const struct vringh *vrh,
> > tmp = cpu_to_vringh16(vrh, val);
> >
> > if (vrh->use_va) {
> > - ret = __put_user(tmp, (__virtio16 __user *)ivec.iov.iovec[0].iov_base);
> > + __virtio16 __user *uaddr = ivec.iov.iovec[0].iov_base;
> > +
> > + if (!access_ok(uaddr, sizeof(*p)))
> > + return -EFAULT;
> > + ret = __put_user(tmp, uaddr);
> > if (ret)
> > return ret;
> > } else {
> >
> >
next prev parent reply other threads:[~2026-10-18 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 7:23 Haoran Wang
2026-10-15 7:42 ` Eugenio Perez Martin
2026-10-17 21:59 ` David Laight
2026-10-18 19:24 ` Michael S. Tsirkin
2026-10-18 19:48 ` David Laight
2026-10-18 21:42 ` Michael S. Tsirkin [this message]
2026-10-18 21:57 ` Michael S. Tsirkin
[not found] ` <CAHk-=wjneFJ7XmZ6ux-LsHq4apDgANcKfERztmAG9sGVY_TxAg@mail.gmail.com>
2026-10-18 22:13 ` Michael S. Tsirkin
2026-10-18 23:12 ` Linus Torvalds
2026-10-18 20:34 ` Linus Torvalds
2026-10-18 21:11 ` Linus Torvalds
2026-10-18 21:41 ` Michael S. Tsirkin
2026-10-18 21:43 ` Michael S. Tsirkin
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=20261018174144-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=david.laight.linux@gmail.com \
--cc=eperezma@redhat.com \
--cc=haoranwangsec@gmail.com \
--cc=jasowangio@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=security@kernel.org \
--cc=virtualization@lists.linux.dev \
/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
all inboxes | Powered by JetHome®