From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Sechang Lim <rhkrqnwk98@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <ljs@kernel.org>
Cc: Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/vma: fix memory leak in __mmap_region()
Date: Wed, 1 Apr 2026 20:44:23 +0200 [thread overview]
Message-ID: <61ef9256-01ea-49a4-9824-be1c3c1fcba5@kernel.org> (raw)
In-Reply-To: <20260331180811.1333348-1-rhkrqnwk98@gmail.com>
On 3/31/26 20:08, Sechang Lim wrote:
> commit 605f6586ecf7 ("mm/vma: do not leak memory when .mmap_prepare
> swaps the file") handled the success path by skipping get_file() via
> file_doesnt_need_get, but missed the error path.
>
> When /dev/zero is mmap'd with MAP_SHARED, mmap_zero_prepare() calls
> shmem_zero_setup_desc() which allocates a new shmem file to back the
> mapping. If __mmap_new_vma() subsequently fails, this replacement
> file is never fput()'d - the original is released by
> ksys_mmap_pgoff(), but nobody releases the new one.
>
> Add fput() for the swapped file in the error path.
>
> Reproducible with fault injection.
>
> FAULT_INJECTION: forcing a failure.
> name failslab, interval 1, probability 0, space 0, times 1
> CPU: 2 UID: 0 PID: 366 Comm: syz.7.14 Not tainted 7.0.0-rc6 #2 PREEMPT(full)
> Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
> Call Trace:
> <TASK>
> dump_stack_lvl+0x164/0x1f0
> should_fail_ex+0x525/0x650
> should_failslab+0xdf/0x140
> kmem_cache_alloc_noprof+0x78/0x630
> vm_area_alloc+0x24/0x160
> __mmap_region+0xf6b/0x2660
> mmap_region+0x2eb/0x3a0
> do_mmap+0xc79/0x1240
> vm_mmap_pgoff+0x252/0x4c0
> ksys_mmap_pgoff+0xf8/0x120
> __x64_sys_mmap+0x12a/0x190
> do_syscall_64+0xa9/0x580
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
> </TASK>
>
> kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
> BUG: memory leak
> unreferenced object 0xffff8881118aca80 (size 360):
> comm "syz.7.14", pid 366, jiffies 4294913255
> hex dump (first 32 bytes):
> 00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N..........
> ff ff ff ff ff ff ff ff c0 28 4d ae ff ff ff ff .........(M.....
> backtrace (crc db0f53bc):
> kmem_cache_alloc_noprof+0x3ab/0x630
> alloc_empty_file+0x5a/0x1e0
> alloc_file_pseudo+0x135/0x220
> __shmem_file_setup+0x274/0x420
> shmem_zero_setup_desc+0x9c/0x170
> mmap_zero_prepare+0x123/0x140
> __mmap_region+0xdda/0x2660
> mmap_region+0x2eb/0x3a0
> do_mmap+0xc79/0x1240
> vm_mmap_pgoff+0x252/0x4c0
> ksys_mmap_pgoff+0xf8/0x120
> __x64_sys_mmap+0x12a/0x190
> do_syscall_64+0xa9/0x580
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> Found by syzkaller.
>
> Fixes: 605f6586ecf7 ("mm/vma: do not leak memory when .mmap_prepare swaps the file")
> Reviewed-by: Lorenzo Stoakes (Oracle) <ljs@kernel.org>
> Signed-off-by: Sechang Lim <rhkrqnwk98@gmail.com>
Acked-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
Thanks!
prev parent reply other threads:[~2026-04-01 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 18:08 Sechang Lim
2026-03-31 19:24 ` Lorenzo Stoakes (Oracle)
2026-04-01 18:44 ` Vlastimil Babka (SUSE) [this message]
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=61ef9256-01ea-49a4-9824-be1c3c1fcba5@kernel.org \
--to=vbabka@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=rhkrqnwk98@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox