From: Mark Rutland <mark.rutland@arm.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: kvm@vger.kernel.org, Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
Kostya Serebryany <kcc@google.com>,
syzkaller <syzkaller@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: kvm/arm64: use-after-free in kvm_unmap_hva_handler/unmap_stage2_pmds
Date: Thu, 13 Apr 2017 14:45:24 +0100 [thread overview]
Message-ID: <20170413134524.GF24027@leverpostej> (raw)
In-Reply-To: <CAAeHK+wJ4Xm+g22V_3fUqfMfP4V7m36FHYzVOFuxH8WbiFcenA@mail.gmail.com>
On Thu, Apr 13, 2017 at 01:53:13PM +0200, Andrey Konovalov wrote:
> On Thu, Apr 13, 2017 at 11:34 AM, Mark Rutland <mark.rutland@arm.com> wrote:
> > I had a go at reproducing this on an arm64 board following [1], but so
> > far I've had no luck.
[...]
> Hi Mark,
>
> You assume that you have KASAN enabled.
Yes; I have KASAN_OUTLINE enabled.
> Since a few unintended line breaks were added in the email, here's the
> program in plaintext:
> https://gist.githubusercontent.com/xairy/69864355b5a64f74e7cb445b7325a7df/raw/bdbbbf177dbea13eac0a5ddfa9c3e6c32695b13b/kvm-arm-uaf-log
Thanks!
> I run it as:
> # ./syz-execprog -repeat=0 -collide=false -sandbox=namespace ./kvm-arm-uaf-log
Thanks again. Having the exact command was very helpful for
sanity-checking my configuration.
In the end, it turned out that in my filesystem, /dev/kvm was not
accessible by the nobody user, so the executor couldn't open it, and
none of the KVM paths were being triggered.
> And it takes less than a second to trigger the bug.
After having chomd'd /dev/kvm appropriately, I can also reproduce the
issue within a second or two, running the same command.
Thanks,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: kvm/arm64: use-after-free in kvm_unmap_hva_handler/unmap_stage2_pmds
Date: Thu, 13 Apr 2017 14:45:24 +0100 [thread overview]
Message-ID: <20170413134524.GF24027@leverpostej> (raw)
In-Reply-To: <CAAeHK+wJ4Xm+g22V_3fUqfMfP4V7m36FHYzVOFuxH8WbiFcenA@mail.gmail.com>
On Thu, Apr 13, 2017 at 01:53:13PM +0200, Andrey Konovalov wrote:
> On Thu, Apr 13, 2017 at 11:34 AM, Mark Rutland <mark.rutland@arm.com> wrote:
> > I had a go at reproducing this on an arm64 board following [1], but so
> > far I've had no luck.
[...]
> Hi Mark,
>
> You assume that you have KASAN enabled.
Yes; I have KASAN_OUTLINE enabled.
> Since a few unintended line breaks were added in the email, here's the
> program in plaintext:
> https://gist.githubusercontent.com/xairy/69864355b5a64f74e7cb445b7325a7df/raw/bdbbbf177dbea13eac0a5ddfa9c3e6c32695b13b/kvm-arm-uaf-log
Thanks!
> I run it as:
> # ./syz-execprog -repeat=0 -collide=false -sandbox=namespace ./kvm-arm-uaf-log
Thanks again. Having the exact command was very helpful for
sanity-checking my configuration.
In the end, it turned out that in my filesystem, /dev/kvm was not
accessible by the nobody user, so the executor couldn't open it, and
none of the KVM paths were being triggered.
> And it takes less than a second to trigger the bug.
After having chomd'd /dev/kvm appropriately, I can also reproduce the
issue within a second or two, running the same command.
Thanks,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
kvm@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
Kostya Serebryany <kcc@google.com>,
syzkaller <syzkaller@googlegroups.com>,
linux-arm-kernel@lists.infradead.org,
Dmitry Vyukov <dvyukov@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvmarm@lists.cs.columbia.edu
Subject: Re: kvm/arm64: use-after-free in kvm_unmap_hva_handler/unmap_stage2_pmds
Date: Thu, 13 Apr 2017 14:45:24 +0100 [thread overview]
Message-ID: <20170413134524.GF24027@leverpostej> (raw)
In-Reply-To: <CAAeHK+wJ4Xm+g22V_3fUqfMfP4V7m36FHYzVOFuxH8WbiFcenA@mail.gmail.com>
On Thu, Apr 13, 2017 at 01:53:13PM +0200, Andrey Konovalov wrote:
> On Thu, Apr 13, 2017 at 11:34 AM, Mark Rutland <mark.rutland@arm.com> wrote:
> > I had a go at reproducing this on an arm64 board following [1], but so
> > far I've had no luck.
[...]
> Hi Mark,
>
> You assume that you have KASAN enabled.
Yes; I have KASAN_OUTLINE enabled.
> Since a few unintended line breaks were added in the email, here's the
> program in plaintext:
> https://gist.githubusercontent.com/xairy/69864355b5a64f74e7cb445b7325a7df/raw/bdbbbf177dbea13eac0a5ddfa9c3e6c32695b13b/kvm-arm-uaf-log
Thanks!
> I run it as:
> # ./syz-execprog -repeat=0 -collide=false -sandbox=namespace ./kvm-arm-uaf-log
Thanks again. Having the exact command was very helpful for
sanity-checking my configuration.
In the end, it turned out that in my filesystem, /dev/kvm was not
accessible by the nobody user, so the executor couldn't open it, and
none of the KVM paths were being triggered.
> And it takes less than a second to trigger the bug.
After having chomd'd /dev/kvm appropriately, I can also reproduce the
issue within a second or two, running the same command.
Thanks,
Mark.
next prev parent reply other threads:[~2017-04-13 13:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 13:34 kvm/arm64: use-after-free in kvm_unmap_hva_handler/unmap_stage2_pmds Andrey Konovalov
2017-03-10 13:34 ` Andrey Konovalov
2017-03-14 11:07 ` Suzuki K Poulose
2017-03-14 11:07 ` Suzuki K Poulose
2017-03-14 11:07 ` Suzuki K Poulose
2017-03-14 16:57 ` Paolo Bonzini
2017-03-14 16:57 ` Paolo Bonzini
2017-04-12 16:19 ` Andrey Konovalov
2017-04-12 16:19 ` Andrey Konovalov
2017-04-12 16:19 ` Andrey Konovalov
2017-04-12 18:43 ` Marc Zyngier
2017-04-12 18:43 ` Marc Zyngier
2017-04-12 18:51 ` Andrey Konovalov
2017-04-12 18:51 ` Andrey Konovalov
2017-04-12 18:51 ` Andrey Konovalov
2017-04-13 9:34 ` Mark Rutland
2017-04-13 9:34 ` Mark Rutland
2017-04-13 9:34 ` Mark Rutland
2017-04-13 11:53 ` Andrey Konovalov
2017-04-13 11:53 ` Andrey Konovalov
2017-04-13 11:53 ` Andrey Konovalov
2017-04-13 13:45 ` Mark Rutland [this message]
2017-04-13 13:45 ` Mark Rutland
2017-04-13 13:45 ` Mark Rutland
2017-04-13 9:17 ` Suzuki K Poulose
2017-04-13 9:17 ` Suzuki K Poulose
2017-04-13 9:17 ` Suzuki K Poulose
2017-04-13 15:50 ` Suzuki K. Poulose
2017-04-13 15:50 ` Suzuki K. Poulose
2017-04-13 15:50 ` Suzuki K. Poulose
2017-04-13 15:53 ` Suzuki K Poulose
2017-04-13 15:53 ` Suzuki K Poulose
2017-04-13 15:53 ` Suzuki K Poulose
2017-04-13 17:06 ` Andrey Konovalov
2017-04-13 17:06 ` Andrey Konovalov
2017-04-18 8:32 ` Mark Rutland
2017-04-18 8:32 ` Mark Rutland
2017-04-18 8:32 ` Mark Rutland
2017-04-18 9:08 ` Mark Rutland
2017-04-18 9:08 ` Mark Rutland
2017-04-18 9:08 ` Mark Rutland
2017-04-18 10:30 ` Suzuki K Poulose
2017-04-18 10:30 ` Suzuki K Poulose
2017-04-18 10:30 ` Suzuki K Poulose
2017-04-20 16:40 ` Suzuki K Poulose
2017-04-20 16:40 ` Suzuki K Poulose
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=20170413134524.GF24027@leverpostej \
--to=mark.rutland@arm.com \
--cc=andreyknvl@google.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=kcc@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=syzkaller@googlegroups.com \
--cc=will.deacon@arm.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.