From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 89EA343F4C5; Mon, 31 Aug 2026 14:06:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788185198; cv=none; b=AuCRoinwnzKVRQ69g+7Ax1PZXgW10S7hJJV1TPjV7BNWeeo9uaAN6QSBeRTlin9gHzguY2AtcWpylStPcj7nt1OmW11TEcdWt6j7fmvnUAF/GpsSXoATv96kLdSPqBnI53peSf9I3XHVBj+IuDGwB3bskOScspPvI6fBE3TrTvI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788185198; c=relaxed/simple; bh=k512HBE5aWXwAISLz6rfFRjDx78i3zL5V46b56hWWjQ=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=qeQ7fPWWU50X8RAykS7xxTKBzIToL5wzPTm0UMe96atFdFB9vQnoGzQ3Fxux1eIu/V0dfiMLgcQvwLu/5tniLdGiV/KpgpjMn3a62uOTLhqhAKlBadyITU1WeCmSMUtfI0rr5qOwUhMeEc7+dI8s73awLfX5mpujvZOUqP8q5VY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ma+8WKFb; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="ma+8WKFb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E47F21F000E9; Mon, 31 Aug 2026 14:06:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788185197; bh=A/cqrToSC1hBWgwHDqc83D08Xb5yOLk1f+Fw3WJcQvk=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=ma+8WKFbdgut0STGC5oyGzzXLknB+UIhqSOf3iQ6LZFS6Xjvb5aDTwLrXqxhCieNM +ngBADdRPp6hgCPLlbEimiZRc9s0TPegrW9n5bs1it3LBuxi6ZYo9IwDQk2YQYXA9w fCy3+Ni8rbKMI965KQF0ThlX0ezUGFi94b5XouIo= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, syzbot+c37bed40868932d790e9@syzkaller.appspotmail.com, wuyankun , Ryusuke Konishi , Viacheslav Dubeyko , Sasha Levin Subject: [PATCH 5.10 18/43] nilfs2: reject invalid block index in GC ioctl Date: Mon, 31 Aug 2026 15:35:26 +0200 Message-ID: <20260831133359.341141534@linuxfoundation.org> X-Mailer: git-send-email 2.55.0 In-Reply-To: <20260831133358.571886287@linuxfoundation.org> References: <20260831133358.571886287@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 5.10-stable review patch. If anyone has any objections, please let me know. ------------------ From: Ryusuke Konishi [ Upstream commit a1735eae55448bc79c2da6593455791e886f6ed8 ] Syzbot reported list corruption caused by a double list_add_tail() call on bh->b_assoc_buffers within nilfs_lookup_dirty_data_buffers(). Analysis revealed that the root cause was the insertion of a page/folio with a page index of ULONG_MAX into the page cache via the GC ioctl. filemap_get_folios_tag(), called by nilfs_lookup_dirty_data_buffers(), repeatedly detects a dirty folio with a page index of ULONG_MAX due to index wrap-around, leading to duplicate processing of dirty buffers. As a preparatory step, the GC ioctl loads the page/folio of the block to be moved during GC and inserts it into the page cache based on information in the nilfs_vdesc structure passed as an argument. Normally, this does not cause issues because the user-space GC library configures the nilfs_vdesc structure properly. However, since there is no range check on the parameters determining the page index, a request with artificially crafted parameters -- such as those generated by Syzbot -- can result in a page/folio being inserted with a page index of ULONG_MAX, triggering the above problem. This resolves the issue by checking the ranges of 'vd_offset' and 'vd_vblocknr' in the nilfs_vdesc structure that determine the page index, thereby preventing the invalid page/folio insertions. Reported-by: syzbot+c37bed40868932d790e9@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=c37bed40868932d790e9 Fixes: 7942b919f732 ("nilfs2: ioctl operations") Cc: wuyankun Cc: stable@vger.kernel.org Signed-off-by: Ryusuke Konishi Signed-off-by: Viacheslav Dubeyko Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- fs/nilfs2/ioctl.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) --- a/fs/nilfs2/ioctl.c +++ b/fs/nilfs2/ioctl.c @@ -544,6 +544,8 @@ static int nilfs_ioctl_get_bdescs(struct * Return Value: On success, 0 is returned. On error, one of the following * negative error codes is returned. * + * %-EINVAL - Invalid virtual block descriptor. + * * %-EIO - I/O error. * * %-ENOMEM - Insufficient amount of memory available. @@ -557,15 +559,30 @@ static int nilfs_ioctl_move_inode_block( struct list_head *buffers) { struct buffer_head *bh; + __u64 limit_blkidx = (__u64)inode->i_sb->s_maxbytes >> inode->i_blkbits; int ret; - if (vdesc->vd_flags == 0) + /* + * vblocknr 0 is reserved as an invalid pointer. Also, limit_blkidx + * ensures that the page index converted from vd_vblocknr never + * overflows the page cache limit and respects the architecture's bmap + * key width. + */ + if (unlikely(vdesc->vd_vblocknr == 0 || + vdesc->vd_vblocknr >= limit_blkidx)) + return -EINVAL; + + if (vdesc->vd_flags == 0) { + if (unlikely(vdesc->vd_offset >= limit_blkidx)) + return -EINVAL; + ret = nilfs_gccache_submit_read_data( inode, vdesc->vd_offset, vdesc->vd_blocknr, vdesc->vd_vblocknr, &bh); - else + } else { ret = nilfs_gccache_submit_read_node( inode, vdesc->vd_blocknr, vdesc->vd_vblocknr, &bh); + } if (unlikely(ret < 0)) { if (ret == -ENOENT)