Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795054409; b=0zkX/u0KDryUqVhtp9xVooNOTKhF4OlTYJO2aoc8TNnbO4Ijv/lbxogMetNjx2wEN2Bb L/pr48FV+SG1H1YGsCCgUazWulxREZGOQC0V+Y05mwut5QQlSuDL0FngRM/No81QukvT/ kKXe2C+C2YSPE96k/s4j4RrD79oTDu37ejCqspYXGYNgiJQNf/H+v6eJHjwYPbCA+DJUr 5LTP5fXRCTBGqr32g1wu+i9OmaSI7WwXQYaBff96wWuouLcifFOnmfyPFpJ7btczmEnLS LUqc4Jj0uiyEpYSfvVprPxL1vkLNzFnUezZAnA1MDHPMp4Hupx5OpfySbTuIoD/nRoQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795054409; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:User-Agent:X-stable:X-Patchwork-Hint: MIME-Version:Content-Transfer-Encoding; bh=GI8DfO0qeNi5YsUs1YCCRnvBn5se1f4c3kXnG9tjTxQ=; b=bhuZBqcL4d3eKhSLahVPtrJ+QWjQb2wucxKaCEOFz5TkoKy/Nyvg+hmh3eVkAj09pVsS 5FoB8M2Q7jq7XDTXtqXkFBWPIKyfbU7Wgbf5BcemybZwz56vN+CrV/WGzx6pY08Qi/84z J+lcB9nFycXguzSwRskcdKqE2eJGQsjS8JwHpLnmG4DkkmKZmiO1nbqsVFYAQ4aSWZ/A6 d2r/I8jeX/Ka7aczDWUhzKBjFmno/VU1fR4EWsQlT//ub/zsocQ6mHSO6vUbRyhsrF+g/ CFEB5bYmJyr5UKrz8i0JUYKr5luOJYKhDYH1IaH+oBPXo3tPxqRmK4KdGoj5Ge1wJvg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=UqCwEORh; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D042B606A333; Thu, 19 Nov 2026 02:13:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=UqCwEORh Received: by smtp.kernel.org (Postfix) with ESMTPSA id 274A41F000C4; Thu, 19 Nov 2026 02:13:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795054409; bh=GI8DfO0qeNi5YsUs1YCCRnvBn5se1f4c3kXnG9tjTxQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=UqCwEORh0Vy4TfAfSqLS0fcIjsThbb2ltHosO+vs9B7zkld7Vw0ujuRLSRhvUWZup c7cPpRLWDi3S66egb+EH5T5Ea6LqdSnBm5oROqP7Czh7r2Czqrtnuk/uZcC65GRztZ 2OlRODVmcBISEEIDBcHNgM6a6tX2ZgksXV20pI3g= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Chris Mason , "Christian Brauner (Amutable)" , Sasha Levin Subject: [PATCH 5.15 1264/2214] aio: fix NULL deref when a fault races ring truncation Date: Wed, 18 Nov 2026 15:49:00 +0100 Message-ID: <20261118150102.194896842@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261118150009.797899913@linuxfoundation.org> References: <20261118150009.797899913@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore X-Mailing-List: patches@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 5.15-stable review patch. If anyone has any objections, please let me know. ------------------ From: Chris Mason [ Upstream commit d53b5aa5cfae27e4d236fc0ab9581085d27f7d33 ] The aio ring lives in a file on the aio pseudo filesystem and the ring VMA uses filemap_fault(). aio_ctx_aops doesn't have a ->read_folio because aio_setup_ring() puts all folios of the ring into the page cache. So a fault on the ring only works as long as it finds its folio in the page cache. If it doesn't, filemap_fault() calls ->read_folio without checking and we jump to NULL. We already fixed this twice this year. A forked child could inherit the ring mapping, fixed by commit c03ce4173c7b ("fs: aio: set VMA_DONTCOPY_BIT in mmap to fix NULL-pointer-dereference error"). And a partial mremap() could leave part of the ring mapped, fixed by commit 3adf7ae18bf4 ("fs: aio: reject partial mremap to avoid Null-pointer-dereference error"). Both times a VMA outlived the ring and the ring file was truncated under it. There's a third way to get there. kill_ioctx() and the error path of ioctx_alloc() unmap the ring with vm_munmap() and ignore the return value. If vm_munmap() has to wait for mmap_lock and a fatal signal is pending it returns -EINTR and the VMA stays. free_ioctx() then calls put_aio_ring_file() which truncates the ring file to zero. A fault that passed the i_size check in filemap_fault() before that doesn't find its folio anymore, allocates a new one and calls ->read_folio: fault on the ring io_destroy() with SIGKILL pending ================= ================================= vm_munmap() returns -EINTR filemap_fault() i_size check passes free_ioctx() put_aio_ring_file() truncate_setsize(inode, 0) no folio, allocate a new one filemap_read_folio() ->read_folio == NULL All that's needed is a second process that shares the mm. If a CLONE_VM child calls io_destroy() and gets SIGKILLed while it waits for mmap_lock the ring stays mapped for the threads of the parent. Any user can do that. Instead of plugging the routes one by one give the ring a ->read_folio that unlocks the folio and returns -EIO. All folios of a live ring are in the page cache so a fault can only end up there if the ring was truncated. The fault now gets SIGBUS. Nothing else reads the ring file and the aio filesystem uses noop_backing_dev_info so there's no readahead either. Making vm_munmap() unkillable in those two places would only close this one route and bring back what commit ae7987835643 ("mm: make vm_munmap killable") fixed. Fixes: 36bc08cc0170 ("fs/aio: Add support to aio ring pages migration") Cc: stable@vger.kernel.org Signed-off-by: Chris Mason Link: https://patch.msgid.link/20261029-work-fs-ai-fixes-v1-1-88f22792f6f7@kernel.org Signed-off-by: Christian Brauner (Amutable) [ sashal: Adapted the folio-based read callback to the page-based readpage API. ] Signed-off-by: Sasha Levin --- fs/aio.c | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/fs/aio.c b/fs/aio.c index 865c94fe4a0c8..86532d483a8ea 100644 --- a/fs/aio.c +++ b/fs/aio.c @@ -454,7 +454,18 @@ static int aio_migratepage(struct address_space *mapping, struct page *new, } #endif +/* + * filemap_fault() reads a page that it did not find in the page cache. All + * pages of a live ring are there, so the ring was truncated under the fault. + */ +static int aio_readpage(struct file *file, struct page *page) +{ + unlock_page(page); + return -EIO; +} + static const struct address_space_operations aio_ctx_aops = { + .readpage = aio_readpage, .set_page_dirty = __set_page_dirty_no_writeback, #if IS_ENABLED(CONFIG_MIGRATION) .migratepage = aio_migratepage, -- 2.53.0