Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 4ED92224895; Mon, 9 Jun 2025 22:52:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1749509555; cv=none; b=g7NaNxCHywgwRKJfVt1pdQ/H38tQKThEwlKoi1PWTH1aVKoaO7yPeAfPa/E85LnsZwFhxIuWuK8lGs+raZ+6gEUKbFh6LhKEJHyk+2WB0xXdZ/jH1Gf62wBmya4qL3exZc816C/xTeWr3lUfk1J4k1rS1X+ZWVDQzX7mfqd6epM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1749509555; c=relaxed/simple; bh=K/3He4YlzTS0OS4zmzm19ApC83LDJtal0YLT3Vtwj88=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=PQndgU1IsiwU8gEDDLNjI9eutiAhISXrmmvyVz+/npedDniz8XS9ziJz+5wiT+DUD5OAtvy38icFig/+3PtHqyEbpqevt3uky106KSWP3GgjfMggyFgR5CopfUnVmal21b8HBJ10EdA8FVouBQH6HFij1Ls++mdVJx7jOEVUPMo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=rPUmB/A9; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="rPUmB/A9" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3B20AC4CEED; Mon, 9 Jun 2025 22:52:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1749509555; bh=K/3He4YlzTS0OS4zmzm19ApC83LDJtal0YLT3Vtwj88=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=rPUmB/A9vyLKOQCB/jPba1/bCpaS8Kz9And7KXmvv8L1rnjplv7U8ic2k9J29JFS3 NBON0JA9AHgQrVK/UvP1xx5jznSNaJRZSrh4RsSS0BuuraToEEf/OzMhhfMyATwDF5 ySNcVQP1YTESOo/jRBnXx9WtAnt8ogYIIyCT0FWICMAHewufZRWDpxvxDqtCGfBY7o GPJboSgTYJSg+5Pq2XX/dkOUgR1wO6TeGV8Ey4sTYs1qRyPnoLxdKfSOhW16Uw89iS WdPTm6g6u2r81jNHSMr1tjeJ5oRTdSsae08MNV2J36oK/R+kyVrcTxhcQmGoA4kCFD 9Snv45XzkXDXA== From: Sasha Levin To: patches@lists.linux.dev, stable@vger.kernel.org Cc: Dmitry Kandybka , Viacheslav Dubeyko , Ilya Dryomov , Sasha Levin , xiubli@redhat.com, ceph-devel@vger.kernel.org Subject: [PATCH AUTOSEL 6.15 08/11] ceph: fix possible integer overflow in ceph_zero_objects() Date: Mon, 9 Jun 2025 18:52:13 -0400 Message-Id: <20250609225217.1443387-8-sashal@kernel.org> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250609225217.1443387-1-sashal@kernel.org> References: <20250609225217.1443387-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: ceph-devel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.15.1 Content-Transfer-Encoding: 8bit From: Dmitry Kandybka [ Upstream commit 0abd87942e0c93964e93224836944712feba1d91 ] In 'ceph_zero_objects', promote 'object_size' to 'u64' to avoid possible integer overflow. Compile tested only. Found by Linux Verification Center (linuxtesting.org) with SVACE. Signed-off-by: Dmitry Kandybka Reviewed-by: Viacheslav Dubeyko Signed-off-by: Ilya Dryomov Signed-off-by: Sasha Levin --- **YES** This commit should be backported to stable kernel trees. Here's my detailed analysis: ## Why This Should Be Backported ### 1. **Clear Bug Fix with User Impact** The commit fixes a real integer overflow vulnerability in `ceph_zero_objects()` where `s32 object_size` is multiplied by `s32 stripe_count` to calculate `u64 object_set_size`. When the layout values exceed 2^31, the multiplication can underflow, leading to: - Incorrect loop bounds in the zeroing logic - Potential infinite loops or premature termination - Data integrity issues during hole punching operations - Incorrect `do_div()` operations ### 2. **Affects Critical Kernel Functionality** This bug impacts core filesystem operations that users depend on: - `fallocate()` system call with `FALLOC_FL_PUNCH_HOLE` - File sparse operations used by databases, VMs, backup tools - Copy-on-write optimizations in Ceph filesystems ### 3. **Small, Contained, and Low-Risk Fix** The code change is minimal and safe: ```c - u64 object_set_size = object_size * stripe_count; + u64 object_set_size = (u64) object_size * stripe_count; ``` This fix: - Promotes `object_size` to `u64` before multiplication, preventing overflow - Has no functional side effects beyond fixing the bug - Maintains consistency with the underlying `u32` data types in `ceph_file_layout` - Cannot introduce regressions ### 4. **Follows Stable Tree Criteria** - **Important bugfix**: Prevents potential data corruption and system instability - **Minimal risk**: Single-line change with no architectural impact - **Confined scope**: Only affects Ceph filesystem's hole punching logic - **No new features**: Pure defensive fix ### 5. **Matches Successful Backport Pattern** This commit is very similar to **Similar Commit #1** (marked YES for backport) which also: - Fixed a type promotion bug affecting critical operations - Had minimal code changes with clear safety benefits - Addressed potential data integrity issues - Was explicitly marked with `Cc: stable@vger.kernel.org` ### 6. **Proactive Hardening Value** While the bug requires specific conditions to trigger (large object sizes or stripe counts), backporting provides: - Defense against potential malicious layouts from compromised metadata servers - Protection for users with unusual but valid filesystem configurations - General robustness improvement for production systems The fix has no downside risk and provides meaningful protection against a real integer overflow scenario that could affect data integrity in Ceph filesystems. fs/ceph/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/ceph/file.c b/fs/ceph/file.c index 851d70200c6b8..a7254cab44cc2 100644 --- a/fs/ceph/file.c +++ b/fs/ceph/file.c @@ -2616,7 +2616,7 @@ static int ceph_zero_objects(struct inode *inode, loff_t offset, loff_t length) s32 stripe_unit = ci->i_layout.stripe_unit; s32 stripe_count = ci->i_layout.stripe_count; s32 object_size = ci->i_layout.object_size; - u64 object_set_size = object_size * stripe_count; + u64 object_set_size = (u64) object_size * stripe_count; u64 nearly, t; /* round offset up to next period boundary */ -- 2.39.5