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 D107447DD64
	for <linux-kernel@vger.kernel.org>; Wed, 17 Jun 2026 15:01:16 +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=1781708480; cv=none; b=gy63No4ubU3FHb1YoInMySClKQ5JgDpW6cC0k+BKG1pK/FWFPtMT6jptIaAV/jH1JQwJLCqZsN8qQg6ZTsrCQnwRnCnUZjy/BWbFR78kuRFCkwdhzbXME5yriea6mmACnjFDrHZ6yZhIHWqys7ZmauGSOf+fLo2N4POQAxMrAPo=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1781708480; c=relaxed/simple;
	bh=ay2GxjfMBj6TdA1VyrvFtq+s5sE85sllMvCM6Qw2M34=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=WpLreo+3ADCTGAhXlptUWU7Kby9nYwJyq1Eu3/yA9nqZGpWLTeHsNaiJ9FLJqyvuahiwcEoYNBa6vevLtLOZQnvYtGhei3pp8r8pz3vsSxmBSTfjL6pmqn3aDoc1YjHAWdjJxeNQJllWE3q85odIRKCS/9q6W3IEgFL/KhJrZMA=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=01gc7Iol; 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="01gc7Iol"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6B1BB1F000E9;
	Wed, 17 Jun 2026 15:01:15 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org;
	s=korg; t=1781708476;
	bh=13w13P+87JLwRzC+QIKRx7CF34LNtnLZFwfwjvhUuR4=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To;
	b=01gc7Iolx2HIIAVTlJtioSk3ShDEec3o6wS07e/r2Eax+dO8TJV5d8z9ERlIixzNY
	 8WlQdbOw4iAzYl3+jOhKrAn4HrB4JKvtnK0Kt1kax0f7gmkWdsm3hb7WGrUR2i1bTs
	 QYq3gZf4sX8nAnYgrIirW2TCDqTYiQIYOFZkyhTE=
Date: Wed, 17 Jun 2026 20:29:59 +0530
From: Greg KH <gregkh@linuxfoundation.org>
To: =?utf-8?B?7J207IOB7Zi4?= <kudo3228@gmail.com>
Cc: kees@kernel.org, linux-kernel@vger.kernel.org, security@kernel.org
Subject: Re: [BUG] ufs: crafted writable mount can overflow cylinder summary
 buffer
Message-ID: <2026061713-extortion-shower-f4f4@gregkh>
References: <CAFvCSAZAQFDo9tJdRCqkstYuyQQ9V5p==S_1z1haOBwcSKMWQg@mail.gmail.com>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAFvCSAZAQFDo9tJdRCqkstYuyQQ9V5p==S_1z1haOBwcSKMWQg@mail.gmail.com>

On Wed, Jun 17, 2026 at 11:42:40PM +0900, 이상호 wrote:
> Hello,
> 
> I am reporting a UFS/FFS mount-time memory corruption issue in
> ufs_read_cylinder_structures().
> 
> A crafted UFS/FFS filesystem image can set inconsistent cylinder-summary
> geometry so that the kernel allocates kmalloc(s_cssize) but copies more than
> that allocation while reading cylinder summary blocks during a writable UFS
> mount.

No need to cc: the security list for this, it's just a "normal" bug to
fix.  Please submit a patch to resolve it if you wish to see it fixed in
the kernel or even better, in the userspace fsck tool.

thanks,

greg k-h