[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e08d4c87-1cc7-ea09-3459-e0d03a920519@suse.cz>
Date: Wed, 18 Oct 2017 13:16:52 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Dmitry Vyukov <dvyukov@...gle.com>,
Chase Bertke <ceb2817@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
syzkaller <syzkaller@...glegroups.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...e.com>,
David Rientjes <rientjes@...gle.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: KASAN: use-after-free Read in do_get_mempolicy
On 10/17/2017 05:55 PM, Dmitry Vyukov wrote:
> On Tue, Oct 17, 2017 at 5:38 PM, Chase Bertke <ceb2817@...il.com> wrote:
>> Hello,
>>
>> I would like to report a bug found via syzkaller on version 4.13.0-rc4. I
>> have searched the syzkaller mailing list and did not see any other reports
>> for this bug.
>>
>> Please see below:
>>
>> ==================================================================
>> BUG: KASAN: use-after-free in do_get_mempolicy+0x1d4/0x740
>> Read of size 8 at addr ffff88006d32fb28 by task syz-executor0/1422
>>
>> CPU: 0 PID: 1422 Comm: syz-executor0 Not tainted 4.13.0-rc4+ #0
Most likely already fixed by 73223e4e2e38 ("mm/mempolicy: fix use after
free when calling get_mempolicy") which landed in v4.13-rc6.
Please focus the fuzzing the latest 4.14-rcX instead :)
Vlastimil
Powered by blists - more mailing lists