From: Greg KH <greg@kroah.com>
To: Daniel Verkamp <dverkamp@chromium.org>
Cc: stable@vger.kernel.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [v4.9, v4.14] vhost/vsock: fix uninitialized vhost_vsock->guest_cid
Date: Thu, 10 Jan 2019 20:12:13 +0100 [thread overview]
Message-ID: <20190110191213.GC18221@kroah.com> (raw)
In-Reply-To: <CABVzXA=82fqF9tBWKS553aLPqmoJThhprzDgXw7F0h4Heuf6bQ@mail.gmail.com>
On Mon, Jan 07, 2019 at 02:49:02PM -0800, Daniel Verkamp wrote:
> Please apply mainline commit a72b69dc083a931422cc8a5e33841aff7d5312f2
> ("vhost/vsock: fix uninitialized vhost_vsock->guest_cid") to the v4.9
> and v4.14 stable branches.
>
> I believe this is the root cause of an issue uncovered by applying
> "vhost/vsock: fix use-after-free in network stack callers" in these
> branches. I sometimes see a crash in hash_del_rcu() with vsock in the
> call stack, and that call is protected by a newly-added check of
> vsock->guest_cid, which was uninitialized before this commit.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-01-10 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 22:49 [v4.9, v4.14] vhost/vsock: fix uninitialized vhost_vsock->guest_cid Daniel Verkamp
2019-01-10 19:12 ` Greg KH [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=20190110191213.GC18221@kroah.com \
--to=greg@kroah.com \
--cc=dverkamp@chromium.org \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).