From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: jasowang@redhat.com, kvm@vger.kernel.org, netdev@vger.kernel.org,
stable@vger.kernel.org, jreuter@yaina.de, ralf@linux-mips.org
Subject: Re: [PATCH] vhost: Check docket sk_family instead of call getname
Date: Fri, 21 Feb 2020 06:11:27 -0500 [thread overview]
Message-ID: <20200221060916-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200221110656.11811-1-eperezma@redhat.com>
On Fri, Feb 21, 2020 at 12:06:56PM +0100, Eugenio Pérez wrote:
> Doing so, we save one call to get data we already have in the struct.
>
> Also, since there is no guarantee that getname use sockaddr_ll
> parameter beyond its size, we add a little bit of security here.
> It should do not do beyond MAX_ADDR_LEN, but syzbot found that
> ax25_getname writes more (72 bytes, the size of full_sockaddr_ax25,
> versus 20 + 32 bytes of sockaddr_ll + MAX_ADDR_LEN in syzbot repro).
>
> Fixes: 3a4d5c94e9593 ("vhost_net: a kernel-level virtio server")
> Reported-by: syzbot+f2a62d07a5198c819c7b@syzkaller.appspotmail.com
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
Thanks for debugging this!
Acked-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> drivers/vhost/net.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
> index e158159671fa..18e205eeb9af 100644
> --- a/drivers/vhost/net.c
> +++ b/drivers/vhost/net.c
> @@ -1414,10 +1414,6 @@ static int vhost_net_release(struct inode *inode, struct file *f)
>
> static struct socket *get_raw_socket(int fd)
> {
> - struct {
> - struct sockaddr_ll sa;
> - char buf[MAX_ADDR_LEN];
> - } uaddr;
> int r;
> struct socket *sock = sockfd_lookup(fd, &r);
>
> @@ -1430,11 +1426,7 @@ static struct socket *get_raw_socket(int fd)
> goto err;
> }
>
> - r = sock->ops->getname(sock, (struct sockaddr *)&uaddr.sa, 0);
> - if (r < 0)
> - goto err;
> -
> - if (uaddr.sa.sll_family != AF_PACKET) {
> + if (sock->sk->sk_family != AF_PACKET) {
> r = -EPFNOSUPPORT;
> goto err;
> }
> --
> 2.18.1
next prev parent reply other threads:[~2020-02-21 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 11:06 [PATCH] vhost: Check docket sk_family instead of call getname Eugenio Pérez
2020-02-21 11:11 ` Michael S. Tsirkin [this message]
2020-02-23 5:43 ` David Miller
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=20200221060916-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=jreuter@yaina.de \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=stable@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 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.