From: Jann Horn <jannh@google.com>
To: syzbot <syzbot+91cf8da9401355f946c3@syzkaller.appspotmail.com>
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, syzkaller-bugs@googlegroups.com,
vbabka@suse.cz
Subject: Re: [syzbot] [mm?] KASAN: slab-use-after-free Read in __mmap_region
Date: Fri, 6 Dec 2024 22:29:39 +0100 [thread overview]
Message-ID: <CAG48ez31brKBFSMW2ANZQAM4P3nzoico3yedtmBv3MK59-eeog@mail.gmail.com> (raw)
In-Reply-To: <67536a25.050a0220.a30f1.0149.GAE@google.com>
On Fri, Dec 6, 2024 at 10:18 PM syzbot
<syzbot+91cf8da9401355f946c3@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: e70140ba0d2b Get rid of 'remove_new' relic from platform d..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13300330580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=50c7a61469ce77e7
> dashboard link: https://syzkaller.appspot.com/bug?extid=91cf8da9401355f946c3
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=124130df980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a280f8580000
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-e70140ba.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/91f313d8125b/vmlinux-e70140ba.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/a9bdf286943a/bzImage-e70140ba.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+91cf8da9401355f946c3@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: slab-use-after-free in __mmap_complete mm/vma.c:2408 [inline]
> BUG: KASAN: slab-use-after-free in __mmap_region+0x1802/0x2cd0 mm/vma.c:2469
> Read of size 8 at addr ffff8880403a6118 by task syz-executor239/5461
This looks like it was introduced by commit 5ac87a885aec ("mm: defer
second attempt at merge on mmap()"), which went into 6.13-rc1? From a
glance it seems like the "vma_merge_existing_range(&vmg)" in
__mmap_region() needs a "vma = " at the start of the line.
next prev parent reply other threads:[~2024-12-06 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 21:18 syzbot
2024-12-06 21:29 ` Jann Horn [this message]
2024-12-06 21:36 ` Lorenzo Stoakes
2024-12-24 12:13 Kun Hu
2024-12-24 16:35 ` Liam R. Howlett
2025-01-16 19:28 ` Liam R. Howlett
2025-01-17 2:13 ` Fudam
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=CAG48ez31brKBFSMW2ANZQAM4P3nzoico3yedtmBv3MK59-eeog@mail.gmail.com \
--to=jannh@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=syzbot+91cf8da9401355f946c3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
/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