From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: tejas bharambe <tejas.bharambe@outlook.com>
Cc: "mark@fasheh.com" <mark@fasheh.com>,
"jlbec@evilplan.org" <jlbec@evilplan.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"syzbot+a49010a0e8fcdeea075f@syzkaller.appspotmail.com"
<syzbot+a49010a0e8fcdeea075f@syzkaller.appspotmail.com>,
"ocfs2-devel@lists.linux.dev" <ocfs2-devel@lists.linux.dev>
Subject: Re: [PATCH v3] ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY
Date: Thu, 2 Apr 2026 11:32:25 +0800 [thread overview]
Message-ID: <df2da2fb-c222-430e-83d6-1855ab34272d@linux.alibaba.com> (raw)
In-Reply-To: <JH0PR06MB663236841A642C2D058C1FD28951A@JH0PR06MB6632.apcprd06.prod.outlook.com>
On 4/2/26 11:10 AM, tejas bharambe wrote:
> filemap_fault() may drop the mmap_lock before returning VM_FAULT_RETRY,
> as documented in mm/filemap.c:
>
> "If our return value has VM_FAULT_RETRY set, it's because the mmap_lock
> may be dropped before doing I/O or by lock_folio_maybe_drop_mmap()."
>
> When this happens, a concurrent munmap() can call remove_vma() and free
> the vm_area_struct via RCU. The saved 'vma' pointer in ocfs2_fault() then
> becomes a dangling pointer, and the subsequent trace_ocfs2_fault() call
> dereferences it -- a use-after-free.
>
> Fix this by saving the inode reference before calling filemap_fault(),
> and removing vma from the trace event. The inode remains valid across
> the lock drop since the file is still open, so the trace can fire in
> all cases without dereferencing the potentially freed vma.
>
> Reported-by: syzbot+a49010a0e8fcdeea075f@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=a49010a0e8fcdeea075f
> Suggested-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> Signed-off-by: Tejas Bharambe <tejas.bharambe@outlook.com>
> ---
> fs/ocfs2/mmap.c | 6 +++---
> fs/ocfs2/ocfs2_trace.h | 10 ++++------
> 2 files changed, 7 insertions(+), 9 deletions(-)
>
> diff --git a/fs/ocfs2/mmap.c b/fs/ocfs2/mmap.c
> index 50e2faf64c..41c08c5a3d 100644
> --- a/fs/ocfs2/mmap.c
> +++ b/fs/ocfs2/mmap.c
> @@ -30,7 +30,7 @@
>
> static vm_fault_t ocfs2_fault(struct vm_fault *vmf)
> {
> - struct vm_area_struct *vma = vmf->vma;
> + struct inode *inode = file_inode(vmf->vma->vm_file);
> sigset_t oldset;
> vm_fault_t ret;
>
> @@ -38,8 +38,8 @@ static vm_fault_t ocfs2_fault(struct vm_fault *vmf)
> ret = filemap_fault(vmf);
> ocfs2_unblock_signals(&oldset);
>
> - trace_ocfs2_fault(OCFS2_I(vma->vm_file->f_mapping->host)->ip_blkno,
> - vma, vmf->page, vmf->pgoff);
> + trace_ocfs2_fault(OCFS2_I(inode)->ip_blkno,
> + vmf->page, vmf->pgoff);
Seems malformed?
> return ret;
> }
>
> diff --git a/fs/ocfs2/ocfs2_trace.h b/fs/ocfs2/ocfs2_trace.h
> index 4b32fb5658..6c2c97a980 100644
> --- a/fs/ocfs2/ocfs2_trace.h
> +++ b/fs/ocfs2/ocfs2_trace.h
> @@ -1246,22 +1246,20 @@ TRACE_EVENT(ocfs2_write_end_inline,
>
> TRACE_EVENT(ocfs2_fault,
> TP_PROTO(unsigned long long ino,
> - void *area, void *page, unsigned long pgoff),
> - TP_ARGS(ino, area, page, pgoff),
> + void *page, unsigned long pgoff),
> + TP_ARGS(ino, page, pgoff),
> TP_STRUCT__entry(
> __field(unsigned long long, ino)
> - __field(void *, area)
> __field(void *, page)
> __field(unsigned long, pgoff)
> ),
> TP_fast_assign(
> __entry->ino = ino;
> - __entry->area = area;
> __entry->page = page;
> __entry->pgoff = pgoff;
> ),
> - TP_printk("%llu %p %p %lu",
> - __entry->ino, __entry->area, __entry->page, __entry->pgoff)
> + TP_printk("%llu %p %lu",
> + __entry->ino, __entry->page, __entry->pgoff)
Ditto.
> );
>
> /* End of trace events for fs/ocfs2/mmap.c. */
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-04-02 3:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 3:10 [PATCH v3] ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY tejas bharambe
2026-04-02 3:32 ` Joseph Qi [this message]
2026-04-02 3:58 ` tejas bharambe
-- strict thread matches above, loose matches on Subject: below --
2026-04-02 4:02 Tejas Bharambe
2026-04-02 4:19 ` Andrew Morton
2026-04-02 3:08 tejas bharambe
2026-04-02 3:47 ` Joseph Qi
2026-04-02 4:17 ` Andrew Morton
2026-04-02 7:09 ` Joseph Qi
2026-04-01 4:20 [PATCH v2] " tejas bharambe
2026-04-01 8:29 ` Joseph Qi
2026-04-01 12:55 ` [PATCH v3] " tejas bharambe
2026-04-02 1:06 ` Joseph Qi
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=df2da2fb-c222-430e-83d6-1855ab34272d@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+a49010a0e8fcdeea075f@syzkaller.appspotmail.com \
--cc=tejas.bharambe@outlook.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