Re: perf: use-after-free in perf_release

From: Peter Zijlstra
Date: Mon Mar 06 2017 - 07:13:48 EST

Next message: Wanpeng Li: "Re: [PATCH v2] KVM: nVMX: reset nested_run_pending if the vCPU is going to be reset"
Previous message: Anshuman Khandual: "Re: [RFC 05/11] mm: make the try_to_munlock void function"
In reply to: Dmitry Vyukov: "perf: use-after-free in perf_release"
Next in thread: Dmitry Vyukov: "Re: perf: use-after-free in perf_release"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, Mar 06, 2017 at 10:57:07AM +0100, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following use-after-free report while running syzkaller
> fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. Note that the task
> is freed right in copy_process due to some error, but it's referenced
> by another thread in perf subsystem.

Weird... you don't happen to have a reproduction case available?

Next message: Wanpeng Li: "Re: [PATCH v2] KVM: nVMX: reset nested_run_pending if the vCPU is going to be reset"
Previous message: Anshuman Khandual: "Re: [RFC 05/11] mm: make the try_to_munlock void function"
In reply to: Dmitry Vyukov: "perf: use-after-free in perf_release"
Next in thread: Dmitry Vyukov: "Re: perf: use-after-free in perf_release"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]