Re: KASAN: use-after-free Read in filemap_fault

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: syzbot <syzbot+b437b5a429d680cf2217@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: KASAN: use-after-free Read in filemap_fault
From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
Date: Sat, 29 Dec 2018 01:01:52 +0300
Cc: akpm@xxxxxxxxxxxxxxxxxxxx, darrick.wong@xxxxxxxxxx, hannes@xxxxxxxxxxx, hughd@xxxxxxxxxx, jack@xxxxxxx, josef@xxxxxxxxxxxxxx, jrdr.linux@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, sfr@xxxxxxxxxxxxxxxx, syzkaller-bugs@xxxxxxxxxxxxxxxx, willy@xxxxxxxxxxxxx
In-reply-to: <000000000000b57d19057e1b383d@google.com>
References: <000000000000b57d19057e1b383d@google.com>
User-agent: NeoMutt/20180716

On Fri, Dec 28, 2018 at 12:51:04PM -0800, syzbot wrote:
> Allocated by task 8196:

...

> Freed by task 8197:

Hm. VMA allocated by one process (I don't see threads in the test case)
gets freed by another one. Looks fishy to me.

-- 
 Kirill A. Shutemov

Follow-Ups:
- Re: KASAN: use-after-free Read in filemap_fault
  - From: Kirill A. Shutemov

References:
- KASAN: use-after-free Read in filemap_fault
  - From: syzbot

Prev by Date: Re: KASAN: use-after-free Read in filemap_fault
Next by Date: Re: 4.14 backport request for dbdda842fe96f: "printk: Add console owner and waiter logic to load balance console writes"
Previous by thread: Re: KASAN: use-after-free Read in filemap_fault
Next by thread: Re: KASAN: use-after-free Read in filemap_fault
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux